12 tips for software testing

313 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
313
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

12 tips for software testing

  1. 1. ©2011 by EliNext Group 12 Tips for Efficient Software TestingA good tester will always spend some time to read softwaretesting good practices first. It will improve jobs accuracy,avoiding unnecessary mistakes.These are 12 tips, experienced and implemented by ElinextGroup Testers.
  2. 2. ©2011 by EliNext Group1) Have a good test plan.A plan should be written by a good and experienced tester (maybeQA leader). A good test plan must encompass all areas of thetesting product and consider budgets, activity definition, scopeplanning, schedule testing, risk identification, staff acquisition,procurement planning and more.2) Understand the product. It is a good practice to involvetesters right from the software requirements and design phase.This way testers can get knowledge of application dependabilityresulting in detailed test coverage. If you are not asked to be part ofthis development cycle then make request to your lead or managerto involve your testing team in all decision making processes ormeetings. Besides, talk more with developers to know moreabout the product.3) Test early, test often. If you want to find bugs, start as early asis possible because a bug found during design stage costs ten timesless to fix than one in coding and a hundred times less than onefound after launch.4) Think positive.Start testing the application with a determination to find bugs anderrors. Don’t think beforehand that there will not be any bugs inthe application. If you test an application with intention to findbugs you will definitely succeed to find even those subtle bugs aswell.5) Go beyond requirement testing. Yes, this is a rule in softwaredevelopment industry. Test application for what it is not supposedto do.
  3. 3. ©2011 by EliNext Group6) Write your test cases during the requirement analysis and designphase. This way you can ensure all the requirements are testable.While writing test cases, write test cases for intended functionalityfirst i.e. for valid conditions according to requirements. Then writetest cases for invalid conditions. This will cover expected as wellunexpected behavior of an application during tests.7) To ensure maximum test coverage break your applicationunder test into smaller functional modules. Write test cases onsuch individual unit modules. Also, if possible, break thesemodules into smaller parts.8) Write clear, descriptive, unambiguous bug report. Do notonly provide bug symptoms but also provide the effects of bugsand all possible solutions. Don’t forget that testing is a creative andchallenging task. Ultimately, it depends on your skill andexperience, how you handle this challenge.9) Make your test cases available to developers prior to coding.Don’t keep your test cases to yourself waiting to get finalapplication release for testing, thinking that you can log more bugs.Let developers analyze your test cases thoroughly to develop ahigh quality application. This will also save the re-work time.10 ) If possible identify and group your test cases for regressiontesting. This will ensure quick and effective manual regressiontesting.11) Applications requiring critical response time should bethoroughly tested for performance. Performance testing is acritical part of many applications. In manual testing this ismostly ignored part by testers due to lack of required performance
  4. 4. ©2011 by EliNext Grouptesting for large data volumes. Find out ways to test yourapplication for performance. If it is not possible to create test datamanually, then write some basic scripts to create test data forperformance test or ask developers to write one for you.12)Take down the new terms, concepts you learn while testing.Keep a text file open while testing an application. Take downtesting progress, observations made during it. Use these notepadobservations while preparing final test release report. This goodhabit will help you provide a complete unambiguous test reportand release details.Finally, I hope this article is useful for you. And the last thing Iwant to say that a good tester working in software outsourcingindustry should share best testing practices, experience withother testers to promote better software all over the world.Written by Quan NguyenFor Elinext Group
  5. 5. ©2011 by EliNext GroupELINEXT GROUPWebsite: http://www.elinext.comEmail: info@elinext.comBlog: http://software-topics.comFacebook: http://www.facebook.com/elinextTwitter: https://twitter.com/elinextDelicious: http://delicious.com/elinextgroup Ireland office Marina House, Adelphi Quay Waterford, Republic of Ireland Phone: +353 (51) 347 477Belarus Development Center Vietnam Development Center155b Bogdanovich St. 37A Phan Xich Long St.220040 Minsk, Belarus Ward 3, Phu Nhuan DistrictPhone: +375 (17) 237 53 65 Ho Chi Minh City, Vietnam Phone: +84 (8) 3995 6849Suggested citation: EliNext Group.2011.“12 Tips for Efficient Software Testing” <http://www.elinext.com/tipstesting>

×