Test cases and it’s briefly explanation and the most allocated test scripts
What is Test Case? This question can hardly be answered in two words. Nevertheless, we try to give a brief description of that concept. Therefore, in order to give a particular bug is necessary to make certain actions, to compare the results with the expected and concluded that there is a bug or not. All of this is the Test Case. Each Test Case is made after the development of a common test plan, in fact, even before the program itself will be written. However, in the absence of the necessary documentation accompanying the software during its life cycle, Test Case can be prepared directly by the testing. The first option is preferable because it provides the highest quality for the minimum period. Writing documentation software developer, of course require a lot of time, especially in the absence of a technical writer, as well as drawing on the tester Test Case, in the absence of a test analyst, but total period of development, including testing, will be significantly lower, by saving time at later stages.
Description of Test Case.
As an example, describe the Test Case can recommend a free utility Test Case Manager (Pierce Business Systems). We offer the following description of the plan:
Test name (briefly reflects its essence).
Steps to play (the description of the actions produced by the tester during the test) followed by numbering each step.
Expected results (what you actually expect from the program during your actions).
The results (what happened in reality).
Evaluation of the passage and the date of the test.
Perhaps this is the minimum list, which should follow the description of Test Case.
Test Script – a set of instructions to automatically check for a certain piece of software.
This test scripts are grouped in a certain trait (egg test functionality). They can be as dependent on the sequence of execution (the result of the preceding is a prerequisite for the next (Test script)), and independent (Test suite).
The most frequently allocated sets are as follows: A set of test scenarios for Smoke-test plan and acceptance testing.
Test scripts are no different. How do we generate huge amounts of testers and script should be able to reuse. It seems strange in a way that both scenarios are often stored against the project. There may be a unit within the project structure for each of the applications being tested, perhaps even determine what version of the script were written against him. Indeed, if the testers constant from one project phase to the next, scripts can be reused.