S
szewong
I'm trying to see if anybody out there has been using this approach. I
have been pushing for a testing method called Joint Rapid Application
Testing. Basically, after system test, you get all resiponsible
parties in a room and intensively go through the program to test the
system. The meeting normally last for 2-4 weeks and everybody goes
through a list of requirements and test the program with real business
data. With developers, BA, testers, DBAs all in a room, we cut down
the communication time and bring the team much closer together. This
also been proven to improve overall product quality.
I found this to be very effective in dealing with logic centric
modules.
Let me know if you have done testing like that.
Sze Wong
Zerion Consulting
http://www.zerionconsulting.com
See my blog: http://szewong.com
have been pushing for a testing method called Joint Rapid Application
Testing. Basically, after system test, you get all resiponsible
parties in a room and intensively go through the program to test the
system. The meeting normally last for 2-4 weeks and everybody goes
through a list of requirements and test the program with real business
data. With developers, BA, testers, DBAs all in a room, we cut down
the communication time and bring the team much closer together. This
also been proven to improve overall product quality.
I found this to be very effective in dealing with logic centric
modules.
Let me know if you have done testing like that.
Sze Wong
Zerion Consulting
http://www.zerionconsulting.com
See my blog: http://szewong.com