This week, we learned about basic project management and the basics of team collaboration in software engineering, including using VCS services such as git, GitHub, and BitLocker.
We also continued our discussion on test-driven development, including test automation. At work, I know several of my team members who have been working on automation efforts for certain tests for a long time, yet as far as I know it has not been an easy effort due to how complex some of these software items are.
Five key principles in creating automated tests are FIRST, which is an acronym that stands for the following:
Fast: Test cases and test subsets should be relatively quick and easy to run, as well as relevant to current coding tasks.
Independent: Tests should not rely on preconditions created by other tests so only the subsets needed can be run.
Repeatable: Tests should not rely on external factors that cannot be controlled, or values that cannot be controlled.
Self-checking: Tests should be able to determine whether they passed or failed without requiring human checking.
Timely: Tests should be written during development and updated accordingly to reflect code changes.
Comments
Post a Comment