Open huynguy97 opened 3 years ago
In order to prevent having to write too much tests for every combination of features we need to try to have some kind of structure.
In order to prevent having to write too much tests for every combination of features we need to try to have some kind of structure.
1. Creating a "base" test that tests all basic functions no matter which combination of features is used 2. Creating a test for when only a single feature is used. 3. Determining which features interact with each other and creating a test for that. Instead of brute forcing tests for every feature combination.
We can still (possibly not necessarily) do the "brute force" but rather than testing everything with all options, just test that the editor actually starts for every combination.
Works well with Google Chrome at the moment. Edge has update issues in Windows and Firefox is stil being figured out.
Need to add IDs to modal buttons. So the buttons that appear in a popup box. E.g. search and replace "replace" button needs an ID.
These files don't work correctly on Firefox, already know the issue but will fix it later.
Using https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Automated_testing and https://www.selenium.dev/ to create some more automated testing.