swapna

• Aug 11th, 2006

 

In some companies you are under pressure to finish testiing even before the requirements doc. is ready. In such situations, you need to attend all the meetings related to the application, take some notes and analyze them.

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• Aug 12th, 2006

 

First of all we go through the application briefly and need to get the functional knowledge and do the adhoc testing upto some extent. Or else if developer is available in the same place the contacthim and got the uncional knowledge.

When ever we got the functional knowledge then next prepare the test cases and go to full fledge testing..

srinivas.

srinivasulub1981@gmail.com

praweenmadavi

 Profile Answers by praweenmadavi 

• Aug 25th, 2006

 

you can apply static black box testing with communicate with the developing team.

Prithvi

• Sep 1st, 2006

 

Test the software and get to know the functionality

Discuss with the developers

Read all the mails related to this project and attend meeting

Prepare Test cases and send it to the team for approval

Do not test unless and until your test cases got approved.

pallavi

• Oct 3rd, 2006

 

First of all ask anybody to give a brif introduction about the project then get details about the module u have to test, start from validating the fields (relating to database design for that component) & gui, report the bugs....(from these may be some invalid but u we get report of invalid bugs & will be help ful in further testing). when u finish one component, u will get idea of database, see the database relationsheep design from database & can start data integration testing!

Best luck!