Hi...

It is compulsary for a tester to study the Design Document for writing integration and system test cases as from the Design Document only u can know the data flow of the project which can be easier for u track the issues why the test cases are failing more efficiently.

Hi

First of all i wanto to tell to all According to my knoledge 'Integration Testing' is not done by 'Test Engineer'.But if there is a chance to Test Engineer to participate in 'Integration Testing'.

Next it is a must to study both Functional Requirement Specification and Design Document to conduct System Testing.

One more thing for a type of 'Adhoc testing' or 'Exploratory Testing' it is not must to study the design document.

HI all

some time Testers also participate in Integration testing By using Grey Box testing techniques at that time he should have some Technical Knowledge .

Let me explain the different type of testing. First low level or unit testing should be done by the developer. Next usually the type of testing that goes on is functional or what some have coin is component testing. Then after the functionality of the code has been verified... you will begin what is call integration testing. Which with integration testing there is the hardware and software is integrated to begin to shake out the defects in the system. At sometime other have referred to this as integration/system testing or end-to-end testing.

So please refer to low level or unit testing which is call white box testing or code base testing for future reference.

Thanks

Interested

Hello

If your definition of Grey box testing relates to backend aka database testing. Then at that respect the tester should be familar with the technical aspect of the requirements and design of the application they would be testing. But to put it more bulk the tester should understand the requirements and design in order to test the product more efficient. How else could one really verify the correctness of the product.

Please understand

Software Testing is a process used to identify the correctness completeness and quality of developement.

Actually. testing can never established the correctness of software as this can ony be done by formal verification (and only when there is no mistake in the verification process)

Therefore software testing can only find defects not prove that there are none. --- Only if Software Quality Assurance is done.

Thanks

Interested

Hi Interested

I am agree with ur answer but u only explained what is integration testing. Can you explain briefly is it neccessary to study the Design document for the tester.

Hi All Goodevening

I am New to this site. I saw some interesting points here. If I'm not wrong here is my view for this question.

I say Yes for this question. Because for understanding the flow of Product/Project we have to go through the design completely. Better if we go ahead like that. We can identify and find the bugs easily while testing and we get good ideas of look n feel also. We can suggest if any thing wrong at the time of design.

If answer is no means We can do without design also but it is difficult to get all the test scenarios and cases to evaluate the ideas.

If any thing wrong in plz let me know correct views...

Thanx