Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Performance and API testing descriptions

...

API Testing

  • Objective: 
    • Validate that data updates GET / POST / PUT requests are processed as expected, based on system requirementsAPI RAML specification
    • Validate any business logic encoded in the API, based on system business requirements
    • Validate that negative test cases have been adequately covered
       
  • Tools:
    • Python scripts
    • Gazoonta tester: Java application uses XML input to make JSON requests to a REST API and  SQL commands to database.
    • Integrate API tests with Travis to Travis-CI: Used to build and then run API tests at build time.after deployment to DEV 
       
  • When: 
    • Ideally, the API tests are written as the API becomes available in the Dev and Test environments.  When test scripts are written during API development, software engineers can use the scripts to test that new development does not have unintended consequences for existing code.

...

  • Objective: 
    • Ensure average response times are consistent with product owner expectations.  
    • Create test scripts based on relevant user scenarios.
    • Calibrate load testing based on system requirements.
       
    • Work with Business Analysts and Project Managers to develop accurate use cases and test scenarios. 
    • Execute load/stress testing based on current and predicted usage metrics
  • Tools: 
    • Blazemeter, JMeter, New Relic, Selenium WebDriver, Taurus 
       
  • When: 
    • Application is available in Test environment

...