skip to content »

Application updating maps software

application updating maps software-41

” A Test Case is simply a list of actions which need to be executed to verify a particular functionality or feature of your application under test. Here is the list of top 13 tips/guidelines which you can keep in mind during test design activities to write test cases which are effective, easily understandable and reusable! Although this is the simplest tip to follow on this list (I feel!), majority of us don’t practice it very effectively – Naming convention for Test Cases!

application updating maps software-90application updating maps software-52application updating maps software-52

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! Effective Test Cases writing and you can acquire it only with practice and in-depth understanding of the application for which test cases are being written.Try to make them make as much sense they can just by looking at the test case ID or test case name! The of a test case should define “What am I going to test?” What needs to be verified, which test environment it needs to be verified in, which test data is to be used – all this information goes into description.For instance, test cases to verify error conditions should be written separately from functional test cases and should have steps to verify the error messages.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: Whatever project you work on, when designing test cases, you should always consider that the Test Cases will not always be executed by the one who designs them.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.

It’s always a good practice to name your test cases in a way that it makes sense to anyone who is going to refer the test cases in future (including YOU! There is a project called “Online” which has a functional area named “Login” Now, I want to write a test case to verify a simple check whether the user is able to login to the website using an email and password.

To keep things simple, instead of naming the tests as TC_01, I could use the below naming convention for my test case so that it gives a brief idea of what the test is for just by looking at its name.

Below are the kind of details you would like to cover as part of this section: and the items I have listed are just an example of what you could include in this section.

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.

As I mentioned in the above point, wherever possible you should attach the relevant artifacts to your test case.