Need to better understand the difference between test scenario and test script (working on plan for unit testing of core system replacement) Saving Changes...
Test Scenario is closely mapped to a Business Scenario/Business Requirement. For example the difference could be the Test Scenario could also include the negative testing objective.
One Test scenario may be mapped or split to many test scripts. Saving Changes...
As a project develops and the testing scope is progressively locked down, the test planning is described in various documents. A typical set of testing project artefacts are as follows:
· Test Scenarios
· Test Strategy
· Test Plans
· Test Scripts
A Test Scenario is a high level description of the kind of testing to be performed for each functional area of the solution. For example, test scenarios might outline the need to test Customer Activation as an end to end business transaction from the customers perspective. It describes the kind of functional testing to be performed in a non-prescriptive fashion typically in a transactional manner.
This typically feeds into a Test Strategy document (sometimes combined with Test Scenarios) that outlines what testing will be performed. For example, a test strategy might define the scope as Unit testing, System Testing, Integration Testing, User Acceptance Testing and exclude Stress & Volume testing. It often also says who is responsible for leading and participating in each test phase or activity. The assignment of these areas of testing enables the test plans and detailed test scripts to be developed.
Test Plans describe how various components will be tested. Test Scripts contain the detail of how each plan is executed and are typically used by testers or by developers to develop automated test harnesses. For example, a test script will describe in detail the end user actions to complete a transaction and the various system responses expected at each stage.
To have an effective Testing Approach, It is better to define the Test Plan in a single document i.e. Test Plan.
Another typical set of testing project artifacts are as follows:
•Test Plan
•Test Strategy
•Test Specifications for Integration Testing.
•Test Specifications for System Testing
•Test Specifications for UAT.
Test Specifications consists of Test senarios and Test Scripts.
All the best.
Saving Changes...
Anonymous
A Test scenario is a set of testcases covering the possible ways of testing a set of conditions in it's entireity(to the fullest).
A test script is a script which is intended to perform a test as directed with a purpose of completing a task. Saving Changes...
Anonymous
Can any one provide sample test script for any web based application.
It would be pretty difficult, and probably not very helpful to you, to post a "generic" test script. The purpose of a script is to step through an application (or process) and test specific aspects.
I usually do this formally first, and if time permits, create a "break script". I try to break the app. ;-) It's a little aggressive, and not always fair, but it's a challenge.
"Every child is born blessed with a vivid imagination. But just as muscles grow flabby with disuse, so the bright imagination of a child pales in later years if he ceases to exercise it."
