I really like Microsoft Test Manager for this because of two things: You don't mention if you're using a test case tool, word, excel or some other method of documentation, but you can adapt what I'm describing to any tool.
Test Review Process When Working With Different Suppliers Test cases are very important for any project as this is the first step in any testing cycle, and if anything goes wrong at this step, the impacts get extrapolated as you move forward in the software testing life-cycle.
Do you need to write test cases in agile testing? So, writing test cases which are effective as well as reusable is very important; good test cases save a lot of time in the later stages of testing really!
Incorporating some simple tips I have given here will help you master the skill of test case writing. Check out the Wikipedia definition here. So here we go… Simple tips for writing effective Test Cases 1.
As a best practice, name the Test Cases to represent the module name or functional area you are going to verify in that test case. Try to make them make as much sense they can just by looking at the test case ID or test case name!
I hope this one was pretty simple.
Enter as much information as possible in the Test Case description! Mainly, you would find the below information in a well-written test case description: Assumptions and Preconditions While writing test cases, you should communicate all assumptions that apply to a test, along with any preconditions that must be met before the test can be executed.
Below are the kind of details you would like to cover as part of this section: Any user data dependency e. Make sure to add as much information as possible for any conditions to be met before running the test case. This list is not exhaustive and the items I have listed are just an example of what you could include in this section.
Test Data Input Identifying test data can be really a time-consuming activity — many a times test data preparation takes most of the time in a testing cycle. It may sometimes need you create a test data afresh as creating a new data might take lesser time compared to identifying it Ask a Tester!
To make your life easy as a tester and your fellow-testers! In many cases where you know the test data can be re-used over time, you can mention the exact Test Data to be used for the test. If the test only involves some values to be verified, you can opt to specify the value range or describe what values are to be tested for which field.
Testing with every value is impractical, so you can choose a few values from each equivalence class which should give good coverage for your test. You could also decide to mention the type of data which is required to run the test and not the real test data value.
The Test Design Steps should not only cover the functional flow but also each verification point which must be tested!
By comparing your Test Case steps with the artifacts Requirement documents, Use Cases, User Stories or Process Maps given for your project, you can make sure that the Test Case optimally covers all the verification points. Attach the Relevant Artefacts As I mentioned in the above point, wherever possible you should attach the relevant artifacts to your test case.
Expected Result A well-written Test Case clearly mentions the expected result of the application or system under test. Each test design step should clearly mention what you expect as outcome of that verification step. Divide Special Functional Test Cases into Sets For effective test case writing, you should consider breaking down your Test Cases into sets and sub-sets to test some special scenarios like browser specific behaviours, cookie verification, usability testing, Web Service testing and checking error conditions etc.
If you strive to write effective test cases, you should write these special functional test cases separately. If while writing these scenarios into sets, a particular feature has a lot of input combinations, you can separate the test into sub-tests.
For example, if you need to verify how the login feature for any application works with invalid input, you can break this negative testing for login functionality into sub tests for different values like: Verify with invalid email-id Verify with blank email-id field and so on… 9.
So, the tests should be easily understandable, legible and to-the-point. Test Case suites that are only understandable by the ones who designed them are ubiquitous. Imagine a scenario where the person who wrote all those Test Cases leaves for some reason and you have a completely new team to work on the Test Case execution, the entire effort spent during the design phase could go down the drain.
If you are the one leaving the organization, you are better off but if you are within the same company but just changed teams, you might be nudged all the time for explaining what you wrote!
You should focus on writing Test Cases that: However, you do need to take care of a few prerequisites for the review process to start because of which the review process could be harmful as well!
That really saves a lot of time! Also, if you get the existing test cases written earlier around the same module, you should be updating those instead of writing new test cases so that for any journey you always have the updated test cases in place.
This might not apply if yours is a new project, however, you can try to write test cases in a way that they could be re-used for some other future project. Always consider updating the existing Test Cases before you start writing new test cases!
Reiterating my point about re-usability, in case of any changes to an existing journey or functionality, you MUST consider updating the existing Test Cases instead of writing any new Test Cases hence avoiding redundancies to the existing set.
This also makes sure you always have updated Test Cases for any journey in your application.Writing the Test Plan After you and your client have agreed upon the scope of the prototype and the test suites to be carried out, it is time to write a plan that describes exactly how you will test them.
Writing test cases can be a time-consuming activity, and approaches vary from comprehensive test plans to more casual and exploratory cases. What factors should influence your approach?
We take a look at a couple of these factors to help you guide your project and team to success. It begins with a suggested approach for assessing and scoping a test project, and offers guidance and best practices.
Writing the Test Plan. Test cases are often classified as being either formal or informal. Hello, If there exists multiple variants of the same test case for example if the same test case had be executed for different countries or different lines of business where the input and output varies but overall steps of execution remains same then below approach i feel would be the better approaches can be used based on the underlying logic or the .
Writing test cases for software takes a little practice and knowledge of the software that’s being tested. Well-written test cases can make your testing process smoother, and save you time in the long run.
By using TestLodge, you can manage and organizes your test cases in an efficient way. A test approach is the test strategy implementation of a project, defines how testing would be carried out. Test approach has two techniques: Proactive - An approach in which the test design process is initiated as early as possible in order to find and fix the defects before the build is created.