newdevs:code:unit-tests
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
newdevs:code:unit-tests [2020/02/12 15:00] – created tmccanna | newdevs:code:unit-tests [2024/09/18 09:39] (current) – add automated test tag sandbergja | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== Unit Tests ====== | ====== Unit Tests ====== | ||
- | When new code is submitted to the Evergreen community for testing and approval, that code should either include step-by-step instructions on how to test bug fixes or automated unit tests to assist in validating new features or significant changes. | + | When new code is submitted to the Evergreen community for testing and approval, that code should either include step-by-step instructions on how to test bug fixes or automated unit tests to assist in validating new features or significant changes. A unit test is typically designed to test a single action (for example, testing that a new database row is created after a form is submitted). |
Guidance on writing step-by-step testing instructions, | Guidance on writing step-by-step testing instructions, | ||
- | **[[: | + | **[[: |
+ | An example of a unit test created by Jane Sandberg during one of our new Developer meetings is available here: | ||
+ | **[[https:// | ||
+ | ===== Videos ===== | ||
+ | |||
+ | [[newdevs: | ||
+ | |||
+ | ===== Things to add to this page: ===== | ||
+ | |||
+ | * Work is being done to deprecate Protractor and replace it with Nightwatch: https:// | ||
+ | |||
+ | |||
+ | |||
+ | {{tag> | ||
newdevs/code/unit-tests.1581537629.txt.gz · Last modified: 2022/02/10 13:34 (external edit)