The document discusses acceptance testing of Lagom microservices with Cucumber. It covers why acceptance testing is important, assumptions about acceptance testing, and how to conduct acceptance testing of a Lagom microservice. The key points are that acceptance testing ensures users don't face bugs, saves time and money, and minimizes impact. It recommends using Cucumber to write automated acceptance tests in a behavior-driven development style, with simple scenario descriptions. This allows for automated accreditation testing on production environments.

1. Presented By:
Himanshu Gupta
Acceptance Testing of
Lagom Microservices
with Cucumber

2. What we will be covered today?
01 Why should we care about Acceptance Testing?
02 Our Assumptions about Acceptance Testing
03 Why should we do Acceptance Testing?
04 How to do Acceptance Testing of a Lagom Microservice?
05 Brief Demo

3. Why should we care about Acceptance Testing?
Companies offer a lot of hosted services
Makes customers happy using
hosted services
Helps in developing
good open source
projects

4. Our Assumptions about Acceptance Testing
1. It’s hard
a. Generating data, setting up test environment.
2. Executing tests is time consuming
a. Business needs everything to be delivered
like today.
b. Or, we fall sick too often
3. Distributed applications are
particularly hard to test.

5. Why should we do Acceptance Testing?
1. So that the Users don’t have to face
such situations.
2. Saves time and $$$
a. Don’t have to work on fixing too many bugs
in production.
b. Have short Dev cycles.

6. Why should we do Acceptance Testing? (contd.)
1. To minimize the impact of bugs
a. Avoid providing wrong results to Users.
b. Avoid doing roll-back of releases.
2. Code mostly fails for some scenarios
a. Users can come up with different scenarios.
b. Someone changed the code due to
misinterpretation.

7. to do Acceptance Testing?

8. Create/Get Data for Tests
1. Generate data manually.
2. Get sample of Production data (if
you lucky :P)
3. Use tools to generate data in an
automated way.

9. Verification
1. Manually test the software.
2. Do code reviews.
3. Write Unit Tests to automate the
testing.

10. Validation
1. Manually test the software on UAT
environment.
2. Write the Integration Test Suites.

11. Accreditation
Manually test the software on Prod
environment

12. Well that's less fun (Right?)
1. Not, if you like
a. Working overtime
b. Bugs

13. Cucumber to the Rescue
1. Encourages BDD
2. Allows Automated Accreditation
3. Acts like a living documentation

14. Create Scenarios (Simple!!!)
Feature: Can I Get Service Offering?
User wants to know whether he/she can Get Service Offering
Scenario: User can Get Service Offering
Given User has Service Offering
When User asks to Get Service Offering
Then User should Get Service Offering

15. Demo

16. Q/A