J-RAT in GUI Centric Testing

So the question is, can we apply J-RAT to GUI Centric Testing? By now we all agree that having all different functional area in the same room during testing increases productivity big time when testing process centric code. Can the same be done for GUI Centric testing? The problem is that during GUI testing, a lot of time is spend in ‘clicking’ through the app and finding bugs. The argument is that having Business Analysts and Developers in the same room doesn’t help this type of testing.

Well, of course that’s not true. J-RAT applies here and J-RAT still rocks.

See my pervious post about the 4 stages in System Test. J-RAT should be apply during the end of stage 1 onward.

What we are doing now is once the tester feels like their bug finding rate is slowing down (meaning they are getting into stage 2), they will start pairing up with developers. One tester and one developer becomes a bug fixing team. They start addressing issues together. There will be multiple ‘bug fixing units’ to address different part of the system.