New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introducing Testing #3579
Comments
Hello everyone, |
@timgrossmann this needs to be top priority. Recent changes have caused massive outages and breaks in code for a lot of people, including me. This is causing some people to flee elsewhere as evident by recent issues opened. I suggest that from here on out, until this is done, only possibly the selenium selectors (as in which HTML elements to select to find the login button, for example) are updated. Also, massive changes like removing Chrome really need more fore-warning - why was this even done? |
In order to make sure that our code base keeps working and new features don't break existing behaviour, we need to introduce tests into the code base. Having a good test coverage also allows us to find problems with changed HTML elements quicker.
Advantages of this feature:
Possible ways of achieving this while keeping control:
Feel free to comment with adjustments and improvements
The text was updated successfully, but these errors were encountered: