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.