From 62d51b7360d652f11c79c9938cef013e2c9eb328 Mon Sep 17 00:00:00 2001 From: Yoni Goldberg Date: Mon, 8 Jul 2019 13:51:54 +0300 Subject: [PATCH] Update aaa.md --- sections/testingandquality/aaa.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sections/testingandquality/aaa.md b/sections/testingandquality/aaa.md index 8d126560..3a3acdf4 100644 --- a/sections/testingandquality/aaa.md +++ b/sections/testingandquality/aaa.md @@ -56,6 +56,6 @@ test('Should be classified as premium', () => {

### "It is important for the test reader to be able to quickly determine what behavior the test is verifying" +From the book [XUnit Patterns](http://xunitpatterns.com/Four%20Phase%20Test.html): -From the book XUnit Patterns(http://xunitpatterns.com/Four%20Phase%20Test.html): -> It is important for the test reader to be able to quickly determine what behavior the test is verifying. It can be very confusing when various behaviors of the system under test (SUT) are being invoked, some to set up the pre-test state (fixture) of the SUT, others to exercise the SUT and yet others to verify the post-test state of the SUT. Clearly identifying the four phases makes the intent of the test much easier to see. \ No newline at end of file +> It is important for the test reader to be able to quickly determine what behavior the test is verifying. It can be very confusing when various behaviors of the system under test (SUT) are being invoked, some to set up the pre-test state (fixture) of the SUT, others to exercise the SUT and yet others to verify the post-test state of the SUT. Clearly identifying the four phases makes the intent of the test much easier to see.