Home

Extend

Hashnode Pro
Hashnode for Agents

Resources

The foreword
Hashnode gql skill

Buildful - AI coding agent that delivers frontier-level results at a fraction of the cost Bug0 - The AI-native e2e QA regression testing Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

Discussion on "Keeping Tests Valuable: Avoid Problems In The Act Blocks" | Hashnode

Feed/

Discussion

Rafael dos Santos Miguel Filho

Software Engineer

Mar 5, 2023

Keeping Tests Valuable: Avoid Problems In The Act Blocks

The Arrange-Act-Assert (A-A-A) convention is widely used when creating unit tests to ensure organization and clarity. Probably most developers have worked with this convention. But even though it is a great convention, we need to be careful about how...

thepragmaticengineer.hashnode.dev12 min read

#web-development #developer #unit-testing #programming-blogs #csharp

Responses1

Markdown supported · ⌘↵ to post

Anthony Fung

Angular/.NET Web developer. I write insights, thoughts, and stories to help software developers build a solid foundation for their skills

Mar 14, 2023

Completely agree that a single-line Act is preferable in most cases.

There are occasionally exceptions to this. One example is when unit testing Observables, it might be necessary to manually advance the test scheduler clock.

Rafael dos Santos Miguel Filho

Software Engineer

Mar 16, 2023

Exactly Anthony Fung, it already falls in frontend cases in specific situations where it was necessary to perform two actions. In most cases this was not necessary. When I began to apply a critical eye more frequently to unit tests, I began to observe that the more actions in a single test method, the more easily it broke.