Page History

...

• Objective: 
  • Ensure average response times are consistent with product owner expectations.  
  • 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 
     
• Timing
  • Performance testing can usually be done when the application becomes available in Test environment.
  • Depending on complexity, performance testing can take from 2 days to 2 weeks.  
  • Allow time in project timeline for mitigation of performance issues.

Regression Testing

• Objective:
  • Validate that set of defined use cases behave as expected
     
• Tools:
  • Selenium WebDriver, Python, HP Unified Functional Testing (UFT)
     
• Timing:
  • For new projects, system requirements should be written such that they can be used as test case scenarios.  
  • Begin executing regression tests when the application is available in the Test environment
  • We see highest Return On Investment when automated regression tests are written during application development.  This allows developers to use the scripts to test that new development does not have unintended consequences for existing code.
     
• Considerations for whether the project would be a good candidate for automated regression tests.  Factors to consider:
  • BA or product owner resources available to help define test cases and validate that automated test scripts cover the needed functionality
  • Stable data set against which to test or ability to seed data for testing
  • Identification and maintenance of authorizations needed in order to run the automated tests
  • Consider the Return on Investment (ROI) for writing automated regression tests for this application
    • Will the tests be used during development phase to validate that new builds do not break existing functionality?
      
    • After release, how often is the application likely to be updated?
    • Will automated regression tests enable the development team to make more frequent releases for bug fixes and enhancement requests?
    • Are there additional factors that necessitate the application being tested on a regular basis? (e.g. SAP Annual Support Packs)
    • Rough estimate of how long it will take to create the automated test scripts. Do objects on the page have unique identifiers which can easily be used in the test scripts? How many test cases are needed?

...