To test Reeborg's World, I use two different testing strategies:
- I run functional/integration tests using Qunit.
For many years, I have been using Chrome as my browser of choice for development. However, after testing the new Firefox version, I am definitely making the change. Here are the numbers, and how I obtained them. I ran each testing sequence 5 times.
After starting my local web browser, for each test with a given browser, I open a private window, paste the url in the address bar and press return. Time to load the page until I see the display, as measured by my watch:
- Chrome (v 62, 64 bits): 12 seconds
- Firefox (v 58, 64 bits): 3 seconds.
Yes, measuring with my watch is not precise; however it is precise enough to distinguish between 3 and 12 seconds.
After loading the page, the tests start in earnest. According to QUnit, the time taken to run the tests is:
- Chrome: between 42 and 43.5 seconds
- Firefox: between 16 and 17 seconds.
So, including the time to load (measured by my watch), it takes approximately 55 seconds to run the test suite using Chrome, and approximately 20 seconds using Firefox.
This is why I am switching to Firefox.
As I was curious, I also tried Microsoft Edge. While Edge can be used apparently without any problems on my public site, it hangs inexplicably when trying to run tests from my local (Python) server.