A Test plan is made up of a large amount of information, a structured, hierarchical outline provides an ideal model for organizing and developing the details of the plan. A test plan consists of two distinct parts
An outline that describes the test requirements
Statement that connect the outline to the Test scripts and testcases that implement the test requirements.
Using the testplan, we can create and run tests.
To start a new testplan :
Select File / New
Select Testplan and click OK.
An empty testplan window opens.
A Test Suite
A Test Suite is a collection of test scripts. Consider a case that we are having a set of script (.t) file. If we want to run these scripts against our application, we have to select the required we have to run the entire script file. But after the completion of that script file, the user has to manually change that to the next script file to run thosetest available in that script. Instead of that silk tests provides a way to continuously select a set of script files and run those script files at-a-stretch. This can be done by creating a new Test Suite file and declare the needed script files in that suite file.
To start a new test suite:
Select File / New.
Select Test Suite and click OK.
In that suite file enter the script file names to run continuously.
Save that script file.
Compile the script file and run it.
Now the process of running the script will not stop after the completion of the first script file, instead of that it will automatically pass to the next script file and run the testcases available there.
In a script file, a test case ideally addresses one test requirement. Specifically, a 4Test function that begins with the testcase keyword and contains a sequence of 4Test statements. It drives an application to the state to be tested, verifies that the application works as expected, and returns the application to its base state.
In the silktest tool, select the File -> Now option the menu bar.
In the resulting dialog box ‘New’, there will be options for selecting different kind of files.
Select the file type 4’ test script’ option.
It will open a new script file.
Before start writing the testcase, declare the necessary file that is to be used in that script file.
Start with the keyword ‘testcase’ followed by the testcase name. The name of the testcase is whatever as selected by the user. But make sure that by looking at the name of the testcase, the objective of the testcase should be understandable.
Start the tests from the scratch so that the silk test will start eh application and to the testing from the base state.
Use necessary conditions / loops if necessary.
At the end of each and every script, print a statement to know whether the test case has achieved its objective or not. The user can make sure that the particular part of the application is error free by looking at the message you print.
Try to make the testcase effective and time consuming (say) by keeping the second tests continue from the place where the first test finishes.
A sample testcase for registering into the yahoo mail.
RELATED POST
ERROR CHECK LIST FOR INSPECTIONS
WALK THROUGHS IN TESTING
TESTING FOR SPECIALIZED ENVIRONMENTS PART ONE
TESTING FOR SPECIALIZED ENVIRONMENTS PART TWO
VALIDATION TESTING
SYSTEM TESTING
DEBUGGING AND TESTING
DEFECT AMPLIFICATION AND REMOVAL
ITERATIVE SPIRAL MODEL
STANDARD WATER MODEL
CONFIGURATION MANAGEMENT
CONTROLLED TESTING ENVIRONMENT
RISK ANALYSIS PART ONE
RISK ANALYSIS PART TWO
BACK GROUND ISSUES
SOFTWARE REVIEWS PART ONE
SOFTWARE REVIEWS PART TWO
SOFTWARE RELIABILITY
SAFETY ASPECTS
MISTAKE PROOFING
SCRIPT ENVIRONMENT
V MODEL IN TESTING
No comments:
Post a Comment