When running automated mobile tests in Rapise, you may experience severe performance degradation in the Android Simulator (Emulator) if you join a video conference or start screen sharing (e.g., using Google Meet via Chrome). The emulator may become 10 to 20 times slower, causing random test failures and timeouts. This article explains how to resolve this hardware contention issue by using a "Google APIs" system image to force Hardware Acceleration.
How do you get the exact time that Rapise takes to load a page? Now, the reports summary shows the overall execution time but if you have pause times between steps then these times are added to the total time of that a page took to display. Customers have asked if Rapise has some kind of function that will allow them to see only the transaction time between pages without the pause times. Does Rapise have something like that? This article provides a solution to these cases.