TEST STRATEGY

TEST STRATEGY

1. TEST PLANNING

   • IMPACT ANALYSIS
     • IS IT ALWAYS DONE?
     • DIFFICULT WHEN REQUIREMENTS ARE NOT CLEAR OR COMPLETE
     • SEPARATE FOR DEV & QA
     • NO ALIGNMENT BETWEEN DEV & QA ABOUT THE RESULTS OF THE ANALYSES
     • DONE BEFORE KICK OFF
   • identify test approach
   • identify test scenarios

2. TEST DESIGN

   • test case creation
   • test data creation
   • test automation creation
   • test environment preparation
   • manual creation of test data
   • highly dependent on developers to update the framework
   • dbscript is not autodeployment enabled

3. TEST EXECUTION

   • automation
   • identifying bugs and issues
   • bug verification
   • definition of done
   • updating of test result in JIRA ticket
   • Identify test cases which will be included in Regression test suites
   • queue messages, logs and db are verified manually
   • Issues are always detected late

4. ST CLOSURE

   • The huge amount of test coverage our Regression test suites have means takes a lot of time running the test.
   • Updating of response files and troubleshooting the current test suites every release takes a lot of time
   • Too many test tools to maintain and reports needs to be consolidated manually.
   • ERS, Italy adapter is mock
   • Portugal and KCS adapter
   • Feature testing will use actual adapters
   • Regression testing will use mock adapters
   • Minimize test cases failing due to changes in test data
   • Restrict our test datas update to ST only
   • Setup new environment for Specflow
   • Remove ST Closure Regression Test - Automation 1.0, 2.0, Specflow, ReadyAPI - 40h Sanity Test - Automation 1.0 - 4h Load Test - Jmeter - 8h Memory Leak Test - Profiler - 2h Parasoft Test (Report) - Executive Report - 0.5h
   • Replace current automation frameworks with a single/centralize automation framework
   • Automate non-functional testing