My experience is test case1 - pass test case2 -pass test case (1+2) = Blocker bug If an user is on xp machine accessing a java application through Citrix neighborhood that uses oracle db residing on solaris server, finds his application running slow -- can't blame the tester.
By
Imaul Mazid, Sr. SE, Aircom International
| 04 16 2010 20:49:39 +0000
Yes I am completely agree with Vishal that while doing Adhoc, Monkey testing we will get such type of bugs which some time will not able to find while running test cases. I beleive becoz I also do adhoc testing on my application and find lots of such tpes of bugs whose test case are not written and i got apprication for that. We have to do adhoc testing for every application becoz nomal user can press or select any thing at that some issue come then the tester will banged by the client wht u left that bug in the application u havent test it properly. So its better we do adhoc testing as well.
By
Tarun Handa, Test Analyst, Electronic Data Sys (EDS) an HP Company
| 08 05 2009 11:06:48 +0000
Yes i agree with you vishal and also designing proper test cases is very vital for the software testing plans, as a lot of bugs, ambiguities, inconsistencies and slip ups can be recovered in time as also it helps in saving one's time on continuous debugging and re testing the test cases.
By
Radhakrishna Marar, Business Analyst, Oracle
| 06 17 2009 12:45:57 +0000
|
Application testing should be properly done. Each "requirement" in the User Specifications should be broken into a "section" in the design. This is linked to a section of the code. There is thus a linkage between the requirements, design and code.The test cases for the same - has to be normally designed and part-coded before the application is coded. The test cases should be documented to say input= xxxx, output = yyyy and the application is tested against these desired outputs for a given input. eq for testing an addition programme 2+3=5 should be known in the test document. Also the boundary cases of addition overflows should be documented. Testing again will be against these documentation. Rigourous sequential testing where the test programme is writtrn before the actual programme is written is a must. Random testing is an additional feature that can be employed. But if all the cases are covered in the design and testing, random testing may not be that important. In te addition case for example we can look at (+)+(+), (-)+(-), (+)+(-), situation causing overflows, underflows when two numbers are added. When you are testing a application, you normally should know the expected result before the application is run. Differences are analysed
By
V. Srinivas, Freelancer, Information Technology
| 04 16 2010 13:39:28 +0000
Yes I agree with you random & adhoc testing is also an important aspects of s/w testing but there is condition also during the testing we can find more bugs during the sequential testing. So we can't say random testing results more bug it totally depends upon the scenario suppose if your test case does not replicate more bug then it may not be the adequate test case.
By
vikash kumar, Software Test Engg, Root Info Solutions
| 04 16 2010 12:19:52 +0000
can't say Random testing is the better to ensure quality of applications, otherwise would have done releases by doing random testing only. If one is getting more bugs while doing random testing/Monkey testing and the bugs are not uncovered while executing the normal test cases in Test plan, it simply reflects the designing of test cases is not adequate. I agree, Random testing is one of the good testing technique to uncover bugs as its oriented towards testers thought and ingenuity of breaking the application as it does not bind the testers scope of testing by restricting the tester to execute whatever writtrn in test cases.
By
Ajit Lal, Sr. Software Associate, Avaya India Pvt. Ltd.
| 01 24 2010 07:02:12 +0000
Most of the offshore testers write the test cases and send it to onshore. The Onshore people blindly execute the test case they will not do adhoc testing and all. Once all the test cases and the traceability matrix is executed successfully they will move the code to production. Thanks, Senthil Vel
By
Senthil Vel, Senior Test Engineer, Stira Technologies
| 07 28 2009 05:34:48 +0000
|