Professional Documents
Culture Documents
Have you
Ever been asked to test a project with no or very less or not to your satisfaction requirements specifications ?
Ever been involved in testing a project which had no test cases or a very little time to create them ? Ever been involved in testing a project in which features/implementation changes dynamically ?
Less Base Language test cases or No Base Language test cases at all The Rapid product changes syndrome Difficulty in seamlessly keeping-up with Product teams milestones Difficulty in dealing with situations when there are no
Something that can help us deal Something that can help us find
with the rapid product changes bugs soon and early testing more scientific
Something that can help us make Regression Something that can help us deal
milestones
We had
We wanted to
Less documentation Lesser base test cases Less time at hand Less chances of timely bugs Less preparedness to deal with chances
Find more bugs Become more responsive to project changes Enhances our chances of meeting internal milestones. Not increase human resources infinitely
10
a code check-in
12
12
Citrix Confidential - Do
Components of a check-in
15
check-in Summary
No.of Lines in the Code that were affected by the Actual Source Code change
Changes
check-in types
check-ins related to Feature Changes check-ins related to Bug Fixes check-ins related to Document Changes check-ins related to Changes in Automation script
17
Check-in types
check-in for feature change
Using check-in Summary and the other details in the source code we could derive ideas for tests
18
Some challenges
Evolving the skill level of the team. Enhance the Developer skills and mix it appropriately with tester mindset to create an irresistible engineering combination. Build rapport/communication with the development team. Building the buy-in for the change in the approach. Imbibing the necessary Sense of urgency within the team.
20
Citrix Confidential - Do
Building accountability in testing. Establishing the focus into specific areas. Knowing how much is tested and how much more needs to be tested. Designing the tests and running them almost at the same time.
What is a session?
Session
Test Design/Execution
Bugs Investigation/Reporting
Session Setup
Test design and execution means scanning the product and looking for problems
Bug investigation and reporting is what happens once the tester stumbles into behavior that looks like it might be a problem
Anything else testers do that makes the first two tasks possible, including configuring equipment, reading manuals, or writing a session report
Session Report
Optimization
Input non-ASCII characters as Input Data (Multi Language Data) Scheduler Automatic analysis of test results Citrix Confidential - Do Not Distributetest Result Auto e-Mail Citrix Confidential - Do
Citrix Confidential - Do
30
Results summary
32
33
The crux of Express functional testing approach It is not the strongest of the species that survive, nor the most intelligent, but the one most responsive to change
References
Images Sources:
Other Credits:
Collgues: Rubina Gonsalves and Shivaraj Shet
http ://www.satisfice.com/sbtm/ http:// satisfice.com/articles/sbtm.pdf