Closed jung-kim closed 2 years ago
Admittedly, tests are slower. A lot of coordinations are added that slowed down. But honestly, tests on the local comp is not too bad.
Hopefully, this PR is to bring stability to the wobbly tests. And hopefully we can make it faster and more efficient. Maybe with pausing the program events triggers thus preventing potential dom changes, which seems to be the main reason why tests are so unstable.
./source/utils/logger.js
, this slimmer and less dependent logger now helps us see browser logs at click tests.waitForNetworkIdle()
(this helped out so much and fixed issues where an element is replaced in between dom detection and dom click.triggerProgramEvents()
to manually trigger program events after certain operations. (this is because certain operations have race conditions where UI fails detects changes because events can trigger before server side can detect it. In real life situations, this is never a issue because mouse movement triggers these events and corrects itself if events are missed)portfinder
dependency rather than inhouse port finding logics.This was so annoying because it passed on my local comp and had to push every single changes to check if passes on github actions...
Also, I'm sure there are few more twicks needed as we go...