Every app has different testing scenarios. What is the actual source of these scenarios??According to me, only requirement document is used to build apps testing scenarios. Is there any other source??Kindly explain it…
Functional Requirements Document, Design Document, System Requirements Document, Business Requirements Document, The code, Client, Business Analysts, Designers, Developers, Fellow Testers, You Imagination and the End Users. All of this are the basis on which you can prepare the test scenarios.
If you are trying to make yourself an authority by saying "According to me" then why ask the question to begin with? However, if you really crave an answer read on. Not all projects get good requirements, and not all tests are clearly identifiable from Requirements. As much as I wish that were so, it is often not the case.
So how do testers generate test scenarios? With their imagination, and drawing upon past experiences and expectations, testers can craft test scenarios to anticipate what they'd want if they were the end user. That means we have to think like the End User, and imagine what kinds of things they might try that the Requirements maybe did not cover. In fact, we ought to be testing more than just what is spelled out in the Requirements, because requirements are rarely EVERY complete. Testers should do as much negative testing as they do checking the happy path as laid out by requirements and use cases especially in the current age of applications.
This is easy, please stop thinking testers are lesser mortals, which is what seems to being inferred here.
Testers are part of a team and as such that team is working towards the same goal, releasing products that customers don't moan about.
These types of questions just continue to perpetuate the illusion that testers are of secondary consideration and alienate testers as something that's different from the development of products.
Stop perpetuating this and ask more positive questions about testing within development teams. As testers are part of those teams.
I use mother wit.
=)
Business Requirement / Specification document helps in developing test cases.
Using BR (business requirement) create Use Case diagrams to create scenario's then split that into multiple test steps to execute the scenario's
Open source tool is available for use case diagram too....
Try that to make it more effective test scenario's to meet the BR (Otherwise called Spec) using use cases
As tester job is to take positive & negative scenario's and security related based on the application which your going to test.
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.