Instead, the system sets up a test environment with, for example, the username abc and the password xyz. Now the system looks like, what if I login with abc and xyz, I should note that login is working fine. Then the system tries to login with abc and uvw or 123 and xyz. In either case, the login may not work well. If all these conditions are met, the test is passed.
These tests are often used nowadays, for example, for example Experiment unit وحدة implemented, testing very specific pieces of code (preferably limited to a single function with input and output). The functionality that checks the login can be tested perfectly with this.
For example, in a well-designed development environment, in a version control system (git), git server automatically runs all unit tests when a pull request is made from a development branch to a master branch. When 100% of the unit tests are achieved (in a larger project in the thousands), then only the pull request can be accepted. If all the tests are not met, the code will not end up in a (previous) version.
[Reactie gewijzigd door Helium-3 op 22 juli 2021 14:59]
“Professional reader. Award-winning gamer. Zombie buff. Social media junkie. Bacon maven. Web scholar.”