Ivan Katunov. Comaqa Spring 2018. Test Design and Automation for Rest API.
Download as PPTX, PDF1 like355 views
The document outlines best practices for testing RESTful API applications, emphasizing the importance of verifying business requirements and employing various test design methodologies. It discusses aspects such as request and response validation, endpoint testing, handling request headers and bodies, and ensuring proper response codes are returned. Additionally, it highlights the need for test automation tools and efficient data handling strategies to enhance testing efficiency.
Ivan Katunov. Comaqa Spring 2018. Test Design and Automation for Rest API.
- 1. Test Design and Automation for REST API Ivan Katunou
- 2. About myself • Software Testing Team Leader and Resource Manager at Epam Systems • 11 years of experience in IT, 8 years in automated testing • Organizer of “Morning Coffee with Automation engineers” meetups • Past projects: • Epam Systems – Hyperion-Oracle • CompatibL – Sberbank, RMB • Viber Media
- 3. Agenda 1. What is special about RESTful API applications? 2. Test design and coverage 3. Automation
- 4. Out of scope • Web services basics • Unit, performance, security testing • How to use tools for REST API testing
- 5. Agenda 1. What is special about RESTful API applications? 2. Test design and coverage 3. Automation
- 7. No UI • Requires additional tools to interact with
- 8. Message Format • XML • JSON • Others
- 9. Resources
- 10. Requirements Except Business Ones • XSD • JSON Schema • WADL (rarely used)
- 11. Stateless In RESTful applications, each request must contain all of the information necessary to be understood by the server, rather than be dependent on the server remembering prior requests. Storing session state on the server violates the stateless constraint of the REST architecture. So the session state must be handled entirely by the client.
- 12. Transfer Protocol • Transfer protocol for RESTful API applications in majority of the cases is HTTP(S). • However it can also use SNMP, SMTP and others
- 13. Implementations Differ REST is an architectural style, implementations might differ • Roy Fielding - Representational State Transfer (REST) • Richardson Maturity Model • What is the Richardson Maturity Model?
- 14. Agenda 1. What is special about RESTful API applications? 2. Test design and coverage 3. Automation
- 15. Test Design and Coverage What to test? How to test? What coverage is good enough?
- 16. RESTful Services by Functionality 1. Provides data 2. Provides data based on some manipulation with data provided to the service 3. Complex operations
- 17. Business Requirements A forecast service
- 18. Business Requirements A forecast service • Provide weather (temperature, precipitation, wind speed) forecast for next 24 hours at different locations • Provide weather forecast for tomorrow, 3 days, 6 days • Provide weather forecast at different locations • etc.
- 19. Business Requirements A calculation service
- 20. Business Requirements A calculation service • Support math operations such as +, -, /, * with integer and float numbers • Support converting numbers from decimal to hex and binary • etc.
- 21. Business Requirements An Internet shop
- 22. Business Requirements An Internet shop • User registration • Searching and filtering products • Adding products to cart • Buying products • etc.
- 23. Business Requirements – Summary • It is crucial to verify business requirements for RESTful applications. • Use common test design approaches (divide into submodules, boundary value analysis, equivalence partitioning, state transition testing, etc.)
- 24. Components
- 26. Endpoints
- 28. Endpoints • Find out which endpoints your web service provides • Each collection endpoint needs to be tested • At least one single resource endpoint needs to be tested for each resource type • Negative tests: • Try to request endpoint that does not exist • Try to request search/filtering/sorting with wrong parameter/value
- 29. Search, Filtering, Sorting Endpoints that support search, filtering, sorting, etc. need to be verified with supported parameters separately and in combinations. Use boundary values, equality partitioning, pairwise testing, check special characters, max length parameters, etc. http://example.com/api/products?q=name:Keyboard&maxPrice:200 http://example.com/api/products?year:2018 http://example.com/api/products?sort:name,asc
- 30. Pagination, Cursors • Endpoints that support pagination, cursors need to be verified with supported parameters separately and in combinations. Use boundary values, equality partitioning, pairwise testing. • For negative tests try to use limit more than max one, offset out of bounds, incorrect values • http://example.com/api/products?limit=20&offset=100
- 31. Versioning
- 32. Request Methods
- 33. Request Methods • GET • POST • PUT • DELETE • OPTIONS • HEAD • PATCH • TRACE • CONNECT
- 34. Request Methods • Positive tests • For each collection endpoint and at least one single resource endpoint for each resource type verify supported request methods • Verify concurrent access to resources (DELETE and GET for example) • Negative tests • For each collection endpoint and at least one single resource endpoint for each resource type try to verify behavior for not supported request methods
- 35. Request Headers
- 36. Request Headers Headers carry information for: • Request body (charset, content type) • Request authorization • etc.
- 37. Request Headers • Positive • For each collection endpoint and at least one single resource endpoint verify all supported request methods with correct header values - with required headers only first, then with verifying optional ones one at a time and combinations. • Use boundary values, equivalence partitioning, pairwise testing. Verify special characters, Unicode text for headers, max length values. • Negative • Verify behavior in case of missing required header, one at a time • Verify behavior in case of wrong/unsupported/empty header value • Verify behavior in case of not supported header
- 38. Request Body
- 39. Request Body Adding user by sending POST request to http://example.com/api/users
- 40. Request Body • Test for endpoints and methods that support sending request body (e. g. POST, PUT) • Verify referenced objects
- 41. Request Body Possible negative tests for POST/PUT requests: • Field contains invalid value (not equals allowed value, out of bounds, etc) • Field of wrong data type • Field value is empty object/string • Field value is null • Required field is absent • Redundant field (“Add to customFields” example) • Empty object {} • Invalid XML/JSON • No data • Post already existing resource
- 42. Request Body Possible negative tests for DELETE requests: • Delete non-existing resource
- 43. Response Codes
- 44. Response codes
- 45. Response codes • Find out which response codes might be returned by your service in which cases • Make sure they are logically related with events (404 for resource not found, 200-201 for resource created) • Try to reproduce such events and verify response codes are correct • Verifying server configuration errors usually out of scope
- 46. Response Headers
- 47. Response Headers Find out which headers might be returned by your service. Test those ones that are related to your service
- 48. Response Body
- 49. Response Body Receive information on particular user using GET request to http://example.com/api/users/1
- 50. Response Body Verify • Structure of a response • Fields • Values • Data types
- 51. Minimal Positive Test For adding a new user
- 52. Minimal Positive Test • Verify the response code • Send POST request • Add only required fields in the request with some correct values • Verify the body of the response • Verify service-specific headers • Add only required request headers • *In case response body is not returned on POST, send GET request for the new item or get from DB
- 53. Other Positive Tests • Required fields only in request body • Test values for each of the fields in separate tests. Verify full response body
- 54. Other Positive Tests • Required fields plus one optional • Test values for the optional field. Verify full response body!
- 55. Complex Request Body • Makes sense to add at least one test with all possible fields • For testing combinations of fields pairwise testing might be leveraged
- 56. Boundary Values for Field Values Find out boundary values - might depend on XML/JSON restrictions, DB, other components
- 57. Transformations
- 59. Caching and Rate Limits
- 60. Rate Limits and Caching • Verify that cached responses received faster • Verify cache expiration time (right before and after) • Find out rate limits for different methods/endpoints • Try to reproduce max allowed rate limit • Try to reproduce more than max allowed rate limit
- 61. Integration with Third Party Stubs can be used to make testing easier and faster, not dependent on actual services
- 62. Coverage
- 64. Third-Party Components No need to test third-party components. Test you application only!
- 65. Risks
- 66. Risks • 1. No testing at all • 2. No requests headers testing • 3. No separate fields of request body testing • 5. No status code testing • 6. No response body testing • 8. No response headers testing • 4. No field values, types, number of occurrence in request body testing • 7. Testing only specific fields in the response body
- 68. Trusted Boundaries • Find out boundary values. “Trust CMS” example • Add notes for trusted boundaries • Verify that those boundaries are still relevant
- 69. Using XSD, JSON Schema • In case web service uses XSD/JSON Schema validation itself additional verification might be minimized • You still need to make sure that application actually does it (check logs for example)
- 70. Difficult to Verify Values • E. g. hash values, current time, random generated values
- 71. Test Automation Including parallel tests
- 72. Test Pyramid
- 73. Test Coverage - Summary • Main challenge - great variety of combinations parameters and values • Depends on time/resources you have and quality you need • No need to test third-party components. Test you application only! • Depends on risks you and the PO are agreed on. How service is used • Depends on trusted boundaries • Depends on additional verification using XSD, JSON Schema by the service • Depends on automated testing, parallel tests execution • Depends on unit, UI tests coverage
- 74. Test Strategy
- 75. Agenda 1. What is special about RESTful API applications? 2. Test design and coverage 3. Automation
- 76. Postman • Use standalone version • Functionality to reduce routine: 1. Pre-request scripts 2. Test scripts 3. Variables, environments, globals 4. Sharing collections 5. Collection runs 6. Mock server 7. Generate code for cUrl, Java, Python, C#, etc. 8. Newman
- 77. Java Libraries • JUnit/TestNG • RestAssured, Apache HTTP Client, other tools and libraries • Gson/Jackson (choose the one that is not used by your team’s developers • JsonAssert
- 78. RestAssured • Usage • Not thread safe (there is a PR that might fix it)
- 79. Test Data Where should it be located? In which format?
- 80. Text • Can be saved as regular text/JSON files at resources folder of your test project or in DB • Hard to change • Can be used for a limited number of tests with all fields and values pre-defined • Maintenance might become a pain in the neck
- 81. Text + Templates Apache FreeMarker Values can be stored in CSV file Still requires much effort for maintenance
- 84. Object Mapping
- 86. Object Mapping
- 87. Object Mapping + Builder
- 88. Object Mapping + Builder
- 89. Object Mapping + Builder • The most convenient approach to work with test data • Working with business objects in tests. Technical details are encapsulated • Saving test data in files/DB is no longer needed • Builder pattern allows chaining adding details for business objects
- 90. Object Mapping + Builder Cannot be (easily) used in the following cases: • Custom fields • Adding null values for specific fields (but not all) • Wrong data type
- 93. Gson/Jackson Objects + Builder
- 94. Gson/Jackson Objects • The most flexible approach for working with JSON/XML in Java • Can be used where Object Mapping cannot be (easily) applied • Requires more effort on developing business objects comparing to Object Mapping • Business object cannot be used for serialization/deserialization. Use wrapped JsonObject instead with its setter and getter
- 95. JSON Schema Validation RestAssured JSON Schema Validation
- 96. Stubs WireMock
- 97. Using DB • Update data and make verifications in DB • Disadvantages: too coupled with DB schemas that might change often and significantly
- 98. Using Java 8 Features Lambdas and Stream API are rather useful for working with collections of data
- 99. Independent Tests Bad Examples: • POST object in one test, GET and verify in another one • Add embedded object in one test, verify it in another one • Shared data with not thread safe access (test data, configs, connection to DB, etc)
- 100. Kotlin Kotlin and API tests presentation by Roman Marinsky
- 101. Automation – Tools to Investigate • SoapUI – REST and SOAP testing tool • RAML/Swagger - for documentation and contract testing • Epam JDI HTTP - Web services functional testing, RestAssured wrapper • Karate - Web services functional testing using BDD style, based on Cucumber - JVM • AWS Lambda - might be used to run API tests in parallel
- 102. Useful links • Presentation samples • Подходы к проектированию RESTful API • Testing RESTful Services in Java: Best Practices • REST CookBook • Status codes • The JavaScript Object Notation (JSON) Data Interchange Format • Introducing JSON • OData • Тестирование API используя TypeScript. Пример технологического стека и архитектуры
- 103. Thank You! Any Questions?
- 104. Contacts • Ivan Katunou, Software Testing Team Leader / Resource Manager at Epam Systems (Coconut Palm test automation team) • [email protected] • @IvanKatunou (Telegram) • +375 29 259 56 42 (Viber, GSM)