You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-6Lines changed: 16 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,12 +76,22 @@ Some concepts and tips to have in mind when writting tests:
76
76
77
77
- Validate only one scenario per test: minimize the number of asserts
78
78
- Tests should be Stateless: all elements in a test should return to the initial state after each test.
79
-
-**F.I.R.S.T**
80
-
-**F**ast - test should be fast. When tests run slow, you won’t want to run them frequently.
81
-
-**I**ndependent - Tests should not depend on each other. Tests should be able to run in any order.
82
-
-**R**epeatable - Tests should be repeatable in any environment. If your test aren’t repeatable in any environment, then you’ll always have an excuse for why they fail.
83
-
-**S**elf-Validating - Tests should have a boolean output. You should not have to read through a log file to tell whether the tests pass.
84
-
-**T**imely - Tests need to be written in a timely fashion. Unit test should be written just before the production code. If you write tests after the production code, then you may find the production code to be hard to test
79
+
80
+
</br>
81
+
82
+
**Arrange > Act > Assert**
83
+
- Arrange – setup the test required elements (variables, objects, databases, mocks, spies, etc)
84
+
- Act – perform the action that will generate the behavior that will be tested
85
+
- Assert – verify the result of the action
86
+
87
+
</br>
88
+
89
+
**F.I.R.S.T**
90
+
-**F**ast - test should be fast. When tests run slow, you won’t want to run them frequently.
91
+
-**I**ndependent - Tests should not depend on each other. Tests should be able to run in any order.
92
+
-**R**epeatable - Tests should be repeatable in any environment. If your test aren’t repeatable in any environment, then you’ll always have an excuse for why they fail.
93
+
-**S**elf-Validating - Tests should have a boolean output. You should not have to read through a log file to tell whether the tests pass.
94
+
-**T**imely - Tests need to be written in a timely fashion. Unit test should be written just before the production code. If you write tests after the production code, then you may find the production code to be hard to test
0 commit comments