Test early without test design/cases. Is this correct in test cycle?

5 pts.
Tags:
Add new tag
Software Quality Assurance
Software testing
Software testing fundamentals
Software testing methodologies
software testing process
test cycle
Hi, I would like to know if anyone has this issue and how to solve it. My test project estimation for each module has been given by Project manager. Each of the testing stage for example test design, test execution, test reporting and retest defects in within a dedicated time. However, most of the time the tester start test design and test execution together. This is to encourage the tester to raise as many defects as possible in the early stage of testing as reasoned by Project manager and existing tester in the team. If tester start testing without test design/cases they will be no formal test result recorded. Is this correct? my company has been practicing this whereby the tester start testing without the formal test cases, they raise as many defects as possible base on req.documentation. While waiting for developer come back for fixes the tester only start creating test cases and insert the test result. I am a new test lead in this company and i found it a bit incorrect but the reason PM gave has make me doubt about it.
ASKED: January 29, 2009  8:38 AM
UPDATED: October 26, 2010  5:58 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Maylee,

This, to me, is a far more complicated question then it may first appear to be.

Not having a detailed insight into you company’s standard process for doing code test, I can, however, give you some of my own common practices that I have accumulated ove thte last 15 + years:

Practice #1: Never assume that code (whether it is a single function or an entire suite of functions to include GUI’s) works properly! Solution: Use a ‘standard’ set of scripts and MANUAL operations to test rudimentary code functinality and validity (‘goes-ins’ and ‘goes-outs’).

Practice #2: ALWAYS use previous test strategies and tools that yielded CONFIRMED bug detection (This is especially true if your test project is a newer (not necessarily BETTER) version of an existing product). Solution: REGRESSION testing! Best to go back as far as three previous versions of the current test target.

Practice #3: Use both ‘dirty’ platforms as well as ‘clean’ platforms to test the (proposed) deployed product. Solution: Find a good utility program that can recreate all of the platforms/versions of OS that the deployed product will be documetated as being able to function properly on. After these ‘clean’ platforms are tested, install both previous versions of the ‘new’ deployed product (if in existence) as well as commonly-used third party software to create a ‘dirty’ platform. This is best done with a re-formatted platform taht has the older/third party software installled FIRST and then install the ‘proposed’ deployed product. Re-run the same tests that you did on the ‘clean’ platforms.

There are more but, these should be a good starting point (from my point-of-view, that is).

Hope this helps.

Anthony

——————————————–

I also find it somehow incorrect.

I think the tester should not design the test cases in the first place. Test cases should be designed in the early stages of the project, even before coding. Often the test cases are derived from the software requirements, so I think that what they are doing is not completely wrong, because they start testing based on requirements.

The problem to me is that without formal test cases defined before hand, the risk of leaving important features/cases without test is bigger. Also, if the tester does not have pre-defined inputs and expected outputs for each test case, he/she has to decide whether the test results are correct or not, and that is also a risk.

Creating test cases after they have been tested, just to be able to write the results, is only helping to document the project, and that should not be its only goal.

On the other hand, if the testing team is often discovering many errors in the early stages of the testing, the development team could also need to improve its job.

-CarlosDL

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Shilpa Venkateshwaran
    I would call this explortory testing. This is a trend when projects are using agile development process.
    2,500 pointsBadges:
    report
  • Suman10125
    Test early without test design/cases. Is this correct in test cycle? Hi there are so many people who are having the sam doubt. But this kind of testing is very common in the IT Industry.. when the Doamin is new and the people whoa re working in the project are new to the Domain then there is a chance of doing this kind of Early testing.Because this type of Exploratory testing wil help in increasing the domain knowledge and give insight to the application. it is not true in all the cases but in a rare situation a person with good domain knowdege can help the new testers
    30 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following