Should it be “Arrange-Assert-Act-Assert”?

by

This is not the most common thing to do, but still common enough to have its own name. This technique is called Guard Assertion. You can find a detailed description of it on page 490 in the excellent book xUnit Test Patterns by Gerard Meszaros (highly recommended).

Normally, I don’t use this pattern myself, since I find it more correct to write a specific test that validates whatever precondition I feel the need to ensure. Such a test should always fail if the precondition fails, and this means that I don’t need it embedded in all the other tests. This gives a better isolation of concerns, since one test case only verifies one thing.

There may be many preconditions that need to be satisfied for a given test case, so you may need more than one Guard Assertion. Instead of repeating those in all tests, having one (and one only) test for each precondition keeps your test code more mantainable, since you will have less repetition that way.

More Related Contents:

  1. Should I test private methods or only public ones? [closed]
  2. What’s the difference between faking, mocking, and stubbing?
  3. What Makes a Good Unit Test? [closed]
  4. When should I mock?
  5. How to terminate a program when it crashes? (which should just fail a unit test instead of getting stuck forever)
  6. How do you mock a Sealed class?
  7. Writing “unit testable” code?
  8. What is the difference between integration and unit tests?
  9. How deep are your unit tests?
  10. Should unit tests be written for getter and setters?
  11. NUnit vs. MbUnit vs. MSTest vs. xUnit.net [closed]
  12. Unit test naming best practices [closed]
  13. How to start working with GTest and CMake
  14. How do I unit-test saving file to the disk?
  15. How to RowTest with MSTest?
  16. Mocking $modal in AngularJS unit tests
  17. How does mockito when() invocation work?
  18. How to test Spring Data repositories?
  19. Is it possible to mock a function imported from a package in golang?
  20. RSpec vs Cucumber (RSpec stories) [closed]
  21. How can I unit test a GUI?
  22. Any way to test EventEmitter in Angular2?
  23. Adding unit tests to legacy code [closed]
  24. Mocking AngularJS module dependencies in Jasmine unit tests
  25. Resharper runs UnitTest from different location
  26. How to mock specific methods but not all of them in Rust?
  27. How to specify test directory for mocha?
  28. Angular 2 Unit Tests: Cannot find name ‘describe’
  29. How do I trigger a keyup/keydown event in an angularjs unit test?
  30. Why should unit tests test only one thing?

Leave a Comment