Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Test a simple workflow. You test that the feature/function works. 
  • No other concurrent workflows or transactions 
  • We do this now BUT we are not always doing this with a large dataset 
  • Provide the dataset. Ask SIGs, etc. 
  • Test done by Development team
  • Can be a standalone user story OR acceptance criteria for a story
  • This test should be deemed as a criteria for definition of done for the feature (sprint level)
  • Can be a test case for Bugfest 

...

  • Test a simple workflow via API. Evaluate performance. 
  • May include concurrent users IF applicable.
  • Test done by Development team
  • May follow these steps to create user story - How Steps to create Performance Testing Scenario (for PO) for PTF Team
  • And review document for proposed SLAs > /wiki/spaces/DQA/pages/2658550
  • This test should be deemed as a criteria for definition of done for the feature (release level) 
  • This test should be run anytime new functionality is added AND for each release to measure any degradations or improvements

...

  • Test a complex workflow.
    • Complex = several actions, concurrent workflows, or concurrent transactions 
  • Single tenant or Multi-tenant environments
  • Test done by PTF team
  • May follow these steps to create user story - How Steps to create Performance Testing Scenario (for PO) for PTF Team
  • AND review document for proposed SLAs > /wiki/spaces/DQA/pages/2658550
  • This test should be deemed as a criteria for definition of done for the feature (release level) 
  • This test should be run anytime new functionality is added AND for each release to measure any degradations or improvements

...