I wish all testers read these software testing good practices. Read all points carefully and try to implement them in your day-to-day testing activities. This is what I expect from this article. If you don’t understand any testing practice, ask for more clarification in comments below. After all you will learn all these testing practices by experience. But then why not to learn all these things before making any mistake?
Here are some of the best testing practices I learned by experience:
1) Learn to analyze your test results thoroughly. Do not ignore the test result. The final test result may be ‘pass’ or ‘fail’ but troubleshooting the root cause of ‘fail’ will lead you to the solution of the problem. Testers will be respected if they not only log the bugs but also provide solutions.
2) Learn to maximize the test coverage every time you test any application. Though 100 percent test coverage might not be possible still you can always try to reach near it.
3) To ensure maximum test coverage break your application under test (AUT) into smaller functional modules. Write test cases on such individual unit modules. Also if possible break these modules into smaller parts.
E.g: Lets assume you have divided your website application in modules and ‘accepting user information’ is one of the modules. You can break this ‘User information’ screen into smaller parts for writing test cases: Parts like UI testing, security testing, functional testing of the ‘User information’ form etc. Apply all form field type and size tests, negative and validation tests on input fields and write all such test cases for maximum coverage.
4) While writing test cases, write test cases for intended functionality first i.e. for valid conditions according to requirements. Then write test cases for invalid conditions. This will cover expected as well unexpected behavior of application under test.
5) Think positive. Start testing the application by intend of finding bugs/errors. Don’t think beforehand that there will not be any bugs in the application. If you test the application by intention of finding bugs you will definitely succeed to find those subtle bugs also.
6) Write your test cases in requirement analysis and design phase itself. This way you can ensure all the requirements are testable.
7) Make your test cases available to developers prior to coding. Don’t keep your test cases with you waiting to get final application release for testing, thinking that you can log more bugs. Let developers analyze your test cases thoroughly to develop quality application. This will also save the re-work time.
8 ) If possible identify and group your test cases for regression testing. This will ensure quick and effective manual regression testing.
9) Applications requiring critical response time should be thoroughly tested for performance. Performance testing is the critical part of many applications. In manual testing this is mostly ignored part by testers due to lack of required performance testing large data volume. Find out ways to test your application for performance. If not possible to create test data manually then write some basic scripts to create test data for performance test or ask developers to write one for you.
10) Programmers should not test their own code. As discussed in our previous post, basic unit testing of developed application should be enough for developers to release the application for testers. But you (testers) should not force developers to release the product for testing. Let them take their own time. Everyone from lead to manger know when the module/update is released for testing and they can estimate the testing time accordingly. This is a typical situation in agile project environment.
11) Go beyond requirement testing. Test application for what it is not supposed to do.
12) While doing regression testing use previous bug graph (Bug graph - number of bugs found against time for different modules). This module-wise bug graph can be useful to predict the most probable bug part of the application.
13) Note down the new terms, concepts you learn while testing. Keep a text file open while testing an application. Note down the testing progress, observations in it. Use these notepad observations while preparing final test release report. This good habit will help you to provide the complete unambiguous test report and release details.
14) Many times testers or developers make changes in code base for application under test. This is required step in development or testing environment to avoid execution of live transaction processing like in banking projects. Note down all such code changes done for testing purpose and at the time of final release make sure you have removed all these changes from final client side deployment file resources.
15) Keep developers away from test environment. This is required step to detect any configuration changes missing in release or deployment document. Some times developers do some system or application configuration changes but forget to mention those in deployment steps. If developers don’t have access to testing environment they will not do any such changes accidentally on test environment and these missing things can be captured at the right place.
16) It’s a good practice to involve testers right from software requirement and design phase. These way testers can get knowledge of application dependability resulting in detailed test coverage. If you are not being asked to be part of this development cycle then make request to your lead or manager to involve your testing team in all decision making processes or meetings.
17) Testing teams should share best testing practices, experience with other teams in their organization.
18) Increase your conversation with developers to know more about the product. Whenever possible make face-to-face communication for resolving disputes quickly and to avoid any misunderstandings. But also when you understand the requirement or resolve any dispute - make sure to communicate the same over written communication ways like emails. Do not keep any thing verbal.
19) Don’t run out of time to do high priority testing tasks. Prioritize your testing work from high to low priority and plan your work accordingly. Analyze all associated risks to prioritize your work.
20) Write clear, descriptive, unambiguous bug report. Do not only provide the bug symptoms but also provide the effect of the bug and all possible solutions.
Don’t forget testing is a creative and challenging task. Finally it depends on your skill and experience, how you handle this challenge.
Over to you:
Sharing your own testing experience, tips or testing secrets in comments below will definitely make this article more interesting and helpful!!
If you are not regular reader of this website then highly recommend you to sign up for our free email newsletter! Sign up just providing your email address below:
63 comments ↓
Nice tips i ever read on software testing on web. i came accross some of these in my career as a tester. We can learn many things by experience. Experience matters then skill..
no# 15) “Keep developers away from test environment.”
is my favorite
Great post! I find 10, 16, and 19 are frequently ignored, but very important.
I like #16, and just apply it recently, then it take much effect, not only for test requirement but also help them to understand clearly to write the test case later.
Thanks for sharing nice tips
(keep going post entry like this, Vjay
Excellent tips — One thing I liked in this was
(11) Go beyond requirement testing. Test application for what it is not supposed to do - which I feel a very important aspect — also end to end testing also needs to be focussed by testers today.
Excellent tips.
Great work, as a tester we always try to find more bugs in the application, but time did not permit for doing all in sequential manner in real time environments. Point # 18: In my last project, I have helped a lot for developers while doing coding (some of the issues were not able to e-mail), but the credit went for the developer in whole team. As a tester we too expect some credits (if I were log in issue tracker, I would get the credit). In this situation how can we help for them without getting any credit?
hi,
The information provided by you is excellent.
I agree with you 100% with the point number 16
16) It’s a good practice to involve testers right from software requirement and design phase. These way testers can get knowledge of application dependability resulting in detailed test coverage. If you are not being asked to be part of this development cycle then make request to your lead or manager to involve your testing team in all decision making processes or meetings
I am following this method for the lat six months so that i can able to understand the each and every single functionality..
I liked # 18 :It true, Increasing conversation with developers we can get know a lot about the product and we can understand the requirement in-depth which in turn will helps in finding more defects
All points are very good.
Mallik
Hiii vijay, I am working as a test engineer. I am working on ERP domain. I am facing lot of problems because 2 times so many errors came from client side. Can you tell me the tips to test web applications based on ERP domain??
this is very good article. Its provide gr8 information
nice
Hello,
Thanks - This article can give more clarification to QA person and substantially also giving idea of testing process to Developers. IT organization should follow and adopt such practices to improve quality process and to maintain quality standards into the organization as well.
Point 16# can be considered as crucial one to enhance and implement best Quality practices!
very nice article.
Very Nice Article………..!!!!!!!!!!!
Very Good Article. It’s really useful.
I’m so much impressed with this site. I would say that I have got a TESTING KHAJANA on this site.
Thank you very much…..
Shardul Kambale
Software Test Engineer
Very nice and interesting article. Imho this definitely covers most relevant topics of good testing practises.
Hi,
Thanks for such a wonderfully tips which we all should follow in our daily routine work. All Points are useful and practical. This is also very useful but very rarely used by people.
Note # 12) While doing regression testing use previous bug graph….
I think we should study the previous bug graph in the following way,
1.Weekly Module wise Bug Report (By this we can understand which Module has more bugs. According we can plan for test cases execution priority, resources etc)
2.Weekly Reporter wise Bug Report (By this we can understand which Reporter is filing more bug, whose bug filing rate is more. We can study it by 80 20 rule)
For efficient and effective testing these 20 tips are very helpful
Note #7) Make your test cases available to developers prior to coding
This will not only save our time but will enhance quality of product.
@ Whyorkay
As I said you should always keep written communication within your team when you discuss/decides any thing in meetings or in peer discussions.
Looking always for credits is not good thing. If you are a good tester, obviously your lead or manager will come to know about it from your work and he/she will give credit for your work.
@ Akshay Gogate
I will address ERP web testing in future articles. Also mail me the exact problem you are facing on ERP web testing.
@Atul
Bug graph by reporter is not useful here. We need to track which modules have more bugs (this may be because of complexity and dependability of module) and accordingly we can distribute the time and efforts for regression testing.
Very Nice & Useful Article…
Xavier
Hi!
This is a wonderful unparallel,unbeatable site & meant for all levels of testers like a quick reference guide.
Thanks to all the people who are involved in keeping this site more lively.
Pavan
Hi,
Nice tips to gain some best working experience in software testing field.All the points are correct in the testing .Again thanks for the article.If not provided i would get these only after two years of experience.
Thanks,
Balaji P.
Nice article and very helpful. And it is very helpful for the tester (or test team) to be involved very early in the project as it costs much less to fix a defect in the requirements phase than in System Integration testing - or later!
However, the timeline for my previous project permitted only 2 weeks each for String and Component testing. And 1 week for System Integration and User Acceptance testing.
Testing included 120+ web screens and 85 Use Cases. Oh yeah, the test team was an army of 1 (as in one). I had many sleepless nights this past summer. The project is now on hold and I’ve been re-assigned.
Really helpful one for the testers….Am sure if we testers follow these points, it will give a pleasant experience for your testing…..
very nice,helpfull article
Really nice tips on testing, Thanks.
Really such a nice article………………and one thing is really most important is that never do verbal communications…..do written communication….. You should have each and every thing in written with you.
It is really good….we all know but do not follow everytime due to……some reason….
Hi,
Can please suggest,For testing a software application a tester should be more talented than a software application developer.Because to create a software limited programming knowledge is sufficient,but to test the same software application more than that application development knowledge is required.Because we have to show that the same application might not work properly.
Thanks,
Balaji Pulikinti
Hi Vijay,
Ur articles sounds great!!!!
I’m involved in Webtop testing which is an application developed by Documentum. Here, we use WDK ATF Test tool for which I need the steps to work on the tool. I went through the developer and user guides but not able to figure out the procedures that are involved.
Thanks in Advance,
RG
Hello,
I would like to thank u for this wonderful article.This will really help for each and every tester.
Hi,
I would like to say one thing ” ITS A PRECIOUS GUIDE THAT EVERY ONE HAS TO READ N IMPLEAMENT FOR TESTING”. I come 2 know that Wht to Do? Wht not 2 Do?
Thanks & Regards,
Saggam
Great Article.
As to # 2 Learn to maximize the test coverage every time you test any application. Though 100 percent test coverage might not be possible still you can always try to reach near it.
This is very abstract, specifically, is there any advice on how to maximize the test coverage? That would be super great.
Hello
What could be the best answer for this:
“If a bug posted by tester is rejected by developer reason being not reproducible.
From tester end bug report consists of screenshot, bug description, steps etc. But developer does not agree. As a tester what be the solution to this? Can we reopen the bug or what??
Hi
Happy to have this guide.
Can anyone suggest good guide for Cppunit test.
All tips are great…!!!
How to test a Web Application based on ERP sysytem
Great Article,
The article is really very helpful , and i have faced many of the issues that are given in the article ,after reading the many things got cleared.
Thnxs for posting this article
Hello to all,
It is really a very good article. I have the same concern as Akshay has with regard to test a web based ERP. I am into testing of web based applications and I am supposed to get involved into testing of web based application. Is there any difference in testing web based app and web based ERP.
Thanks
(Please ignore first one, written again due to typo error)
Hello to all,
It is really a very good article. I have the same concern as Akshay has with regard to test a web based ERP. I am into testing of web based applications and I am supposed to get involved into testing of web based ERP. Is there any difference in testing web based app and web based ERP.
Thanks
Hi, I have been reading on u r web for a while. its really good. I request you to put a nice article on webservices testing ASAP pleae. ITs a emerging trend now and most of the people ask for it.
Hi All,
This site is really too good for the testers,whenever i read articles from this site it boosts up my enthusiasm in testing.
Hi again,
I am working as a test engineer since 1.5 yrs & i do exploratory kind of testing so no documents are maintained.As its being mentioned above that “Write your test cases in requirement analysis and design phase itself. This way you can ensure all the requirements are testable.”
Kindly give me more information regarding it as i have not dealt practically ,so that i can groom myself.
Thank You.
nice article.
What is negative and positive testing and negative test case
[…] testing help blog - I found the sample bug report and practical software testing tips to be […]
All Tips given in the article are really good
Still my favorites are 11, 16 and 18
Tip11 it helps to find more and more bug which are not covered in requirement and not covered requirement can easily identified, by tip 16 and 18.
Tip 16 helps us to understand the full product right from the beginning hence we can play more and more in and around the application and also helps to make decisions
Tip18 it helps much more understanding of product and by communicating with developer by this we can easily identified the random changes and we maintain the good relation ship
Thanks Vijay for Good tips
Article is very good and extremely useful to testers novice/experts as it deals with various if nuances of testing.
I am a techno banker. I have 15 years of Banking and 12 years of software exposure- exposure to full sdlc.
srs,design,coding,implementation. I need to do some certification in testing and quality. Some body please suggest any institute/organisation in Bangalore for the same.
thanks.
I am new to the testing , these 20 points very useful to me , realy thanks to you , continiously give these type of testing tips
by
Syed
good tips
good one
don’t keep anything verbal!
I must remeber it clearly, I think it’s very important.
Respected seniors, Vijay plz. answer me.
How to answer - “what METRICS do you use? How many types of metrics are there?” It’s a most imp question in interviews. As far as i know, different metrics are–Defect Density, Defect Leakage, Traceability Matrix, Bug Trend Analysis(means comparing no of bugs in different versions). Types of Metrics are Process, Product, Project. “Do CMM, ISO 9000 come under Metrics?”. I am not concluding the above information. My attempt is to make clear that on what topic seniors have to give their kind and valuable suggestions.
Plz. respond with full details.
Yours faithfully………Sirisha
hello sir/madam,
actually, how many types of “Test Reports” are there?
i came through different terminology like—
Test summary reports
Test execution reports
Test status reports
Test log reports
Test daily, weekly reports
These all mean same??? if not please explain me and also explain me if there are any other reports that come under above list. in the least case please provide me exact link. Thanks in advance.
Very Intresting and Nice article to be read by all testers.
Very Intresting and Nice article to be read by all the testers.
plz give me tips about testing
Nice article…… will help testers carve out their testing approach
Good tips.
Nice Tips
Great article, i really love point #16
Cheers Ya
The thing is Bobby, if everyone is involved in software meetings, there is no opportunity for people to relax while the managers are out of the room.
Leave a Comment