What are your most favourite software testing tips? (Poll Closed) (poll 3374501)

What are your most favourite software testing tips? (Poll Closed)

Testers only need 5 steps ato gather the right information and get a clear overview http://tinyurl.com/3azbh8h 0% (0 votes)
Testing is fun and challenging so never think that u have not much to contribute, little value in doing it or not stretching u enough 1% (2 votes)
Testing "Learning is like rowing upstream: not to advance is to drop back" proverbs http://bit.ly/bVRTKT 7% (14 votes)
Be humble when reporting defects, gloating often creates resentment. Besides, the defect could be your testing. 4% (8 votes)
Always make a testreport, even if no one asks for it. You will at least analyze your own work and will learn a lot from it. 3% (6 votes)
like puppies, devs need positive reinforcement. instead of scolding them for mistakes, reward their help+fixes with praise+cookies. 2% (5 votes)
When automating tests,keep clean log mssgs that are easy to interpret towards debugging 2% (5 votes)
When automating tests,ensure all value I/P are parametrizd to buildin scope exploratoratory Testng 2% (4 votes)
thinking like an end user as you test - can help you identify critical risks most of the time 1% (2 votes)
device testing?good scenarios include end user's real time entries.Talk to users as u build them <1% (1 vote)
testdata cleanup-important activity.Understand implication to ur test result if not used B4 each execution cycle 1% (3 votes)
want to be a good tester? Look beyond only conforming the requirements given 2% (4 votes)
Simple load testing ideas with potentially big returns - @PerfDan Tech Blog; http://tinyurl.com/24chqcb <1% (1 vote)
Next time you need sample text, don't go for boring lorem ipsum, use ascii art instead http://twurl.nl/tr0uay http://www.figlet.org/ 1% (2 votes)
When looking at software, if something looks funny, investigate it! Chances are, it'll lead you to a bug! 3% (6 votes)
Use #Virtualization for test optimization (cover number of platform in low cost) 1% (2 votes)
For testing with proxy try using #FoxyProxy http://bit.ly/aJKI76, switches Internet connection based on URL pattern 1% (2 votes)
"If a decision maker relies on the number of passed test cases, make him aware of his confirmation bias" 1% (2 votes)
Learn about technical writing at http://bit.ly/ZymC6 to boost your bug reporting skills <1% (1 vote)
Instead of typing any char for invalid password try passwd ' OR '1'='1. We might be able to cover important security bug here 3% (6 votes)
Don't force your approach of only truth of testing to be accepted, make it work and it will be accepted adn if not change it <1% (1 vote)
Visit User forums discussing your application regularly to see pain of your mistake and see how can we reduce it in current cycle <1% (1 vote)
To see if your app is not bugged by #y2k38 test with 2038 as test date for Date value. For y238 problem http://bit.ly/HgaZ1 3% (7 votes)
Try to break this, "i don't have enough time to test" :) 2% (5 votes)
Make 32767 and 65535 as part of your numeric test data as these are the highest value that signed and unsigned integer can hold 5% (11 votes)
Cargo Cult Science by R. Feynman, http://tinyurl.com/3xwv369 somthing we can learn from 1% (3 votes)
FeatureSwap is oen of the method to have a planned AdHoc Testing <1% (1 vote)
When agreeing Non-Functional Requirements, ensure they are a)realistic, b)testable and c)measurable 1% (3 votes)
Do walk-throughs with ur developers where u review their code and they review ur tests. U'll be amazed of the value gained! 2% (5 votes)
effectively voicing objections to decisions made by your superiors is a key part of a tester's job. be courageous! 1% (2 votes)
If yr mnager havnt hrd of Cem Kaner @JerryWeinberg @lisacrispin @michaelbolton @curioustester @jamesmarcusbach @testingclub, tell him 1% (2 votes)
Follow @dailytestingtip for some real good tips. 9% (19 votes)
Help developers not2reject ur defect.Ensure u add clear steps2replicate defect&proof of testing when u report defects 1% (3 votes)
Good testers don't "evolve" in their careers to programmers, analysts or managers. They become GREAT testers. 5% (10 votes)
do not take requirements for granted.Question till u get answer to every how and why!! 2% (4 votes)
To find some cool ideas (and new people in testing to follow), browse the list of contributors to dttip... <1% (1 vote)
@alanpage Thanks for pointing out. Found good compilation of numeric test data based on storage http://bit.ly/9wDiFt 0% (0 votes)
Writing is a good way to stimulate learning and critical thinking. http://bit.ly/apkNbC 2% (4 votes)
Think testing as a challenge; it is not simply verification and validation of what is written and communicated in the starting 10% (21 votes)
Be the person that talks to the developers, management, users, analist and anyone else you can find 1% (3 votes)
An oracle is required to recognize a problem. However, don't assume the problem is w/in the program. It could be the oracle. 3% (6 votes)
Allow test resources to work in every area of AUT, will get best product out form the team. <1% (1 vote)
The numbers and statistics generated from test execution do not always show you the right product health. Look beyond test execution <1% (1 vote)
"Testmanager? testconsultant? testanalyst? testcoördinator? whatever!... just call me a TESTER!... and bloody proud of it!" 4% (9 votes)
Smoke is only an indicator of smoke. Open flames indicate a fire. All else is just heat ... or cigarettes. <1% (1 vote)
To share your PC screen on short notice, try SharedView -- free, fast, and easy (1 min setup): http://bit.ly/ab58r8 <1% (1 vote)
Make reusability of your testware and testideas a priority 2% (5 votes)
Don't think only of the bugs you will find, but the goals of the organization that will be using the software 2% (4 votes)

Total Votes: 210

1 Comment

David Webb - 13 years ago

The various Roles and Responsibilities of a Tester

Requirement Analysis - in case of doubt check with counter parts or specialists.
Test design - Always clarify, never assume and write.
Review of Other Test design documents.
Approving Test Design documents.
Test Environment setup.
Test results gathering.
Evaluation of any tools if required. - ex. QTP, Valgrind memory profiling tool.
Mentoring of new joinees. Helping them ramp up.

What are your most favourite software testing tips? (Poll Closed)

1 Comment

Leave a Comment

Give others the chance to vote.

Create your own.