The idea is that we can have various guidelines to do the testing and document is just one of them.
So, in order to make your team member busy, let’s try some ideas:
1) Have team read that document and start testing the system. Note down any problem while they explore the products
2) If your system is complex or need specific domain knowledge, let’s team research and get familiar with the system or have them trained
3) Prepare environment to test. Take a big picture and see what you need to prepare for team to do the testing. Does team need any specific tools, applications, hardware, network, support devices
Hey Rita,
If SRS is not ready, this is a good time …to test!
Not sure if you know this but Michael Bolton wrote great article about this: Testing Without a Map (You can download here: http://www.developsense.com/articles/2005-01-TestingWithoutAMap.pdf )
The idea is that we can have various guidelines to do the testing and document is just one of them.
So, in order to make your team member busy, let’s try some ideas:
1) Have team read that document and start testing the system. Note down any problem while they explore the products
2) If your system is complex or need specific domain knowledge, let’s team research and get familiar with the system or have them trained
3) Prepare environment to test. Take a big picture and see what you need to prepare for team to do the testing. Does team need any specific tools, applications, hardware, network, support devices
Goodluck with your project
-Thanh