[slinkanand]

Testing tasks start during the development of requirements (reviewing the requirements to determine if each requirement can be tested as stated). In addition this is the time when preliminary palnning must take place (how will the software be tested and what resources are need (Hardware, software, and people). Each step in the development process has a role for testing/QA . Some organizations allow this (it reduces life cycle costs by finding problems early in the development lifecycle). The actual testing of code should be first performed by the developing organization (unit tests), sometimes complex designs are tested by systems level people using simulation/modeling tools before coding starts. Doing the job right costs more money up front, but greatly reduces costs after deployment to Users.
Testing by personnel outside the development organization should start as the pieces are integrated (unit integration). This allows a second set of eyes to look at the product as the software evolves.

[au123]

Hi
I am agreed with ur words, but I want to clarify the exact point for the question that is "When exactly the testing starts in software development life cycle?"

My answere is :

As u can understand Testing was earlier a part of SDLC but now it is a independent Idendified process which basically concened about quality of the product. So the answer would be as soon as Tester get build i.e., .exe files they start applying their written testcase on released build which is called "Test Execution" after that bug reporting and test management as well as regression things come to the picture.

So If we talk about Tester then then comes into picture after getting build.

Thanks and regards
Ashok

Originally Posted by slinkanand

Testing tasks start during the development of requirements (reviewing the requirements to determine if each requirement can be tested as stated). In addition this is the time when preliminary palnning must take place (how will the software be tested and what resources are need (Hardware, software, and people). Each step in the development process has a role for testing/QA . Some organizations allow this (it reduces life cycle costs by finding problems early in the development lifecycle). The actual testing of code should be first performed by the developing organization (unit tests), sometimes complex designs are tested by systems level people using simulation/modeling tools before coding starts. Doing the job right costs more money up front, but greatly reduces costs after deployment to Users.
Testing by personnel outside the development organization should start as the pieces are integrated (unit integration). This allows a second set of eyes to look at the product as the software evolves.

[slinkanand]

Hi Ashok,

i like the way u replied to my post....i really appreciate that....

In your understand of testing any activity related to testing,you should consider the testing strategy, or testing aproach which starts at the early stages in the project, even before requirements gathering.If you refer only to tests running, that's depending on existing methodology, and could occur after requirements gathering, during design, or even after the product is developed (which is not the best approach, but unfortunately still used).
QA activities should start from the very begining, in order to define the development processes, checkpoints,...


hit me back with ur suggestions..

Cheer's

[das.testing]

Hi,

Gud work Anand & Ashok, Keep going....

Regards

Arun