home.social

#acceptancetests — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #acceptancetests, aggregated by home.social.

  1. Acceptance Tests and Unit Tests as Documents First, Tests Second

    The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]

    kerrick.blog/posts/2025/accept

  2. Acceptance Tests and Unit Tests as Documents First, Tests Second

    The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]

    kerrick.blog/posts/2025/accept

  3. Acceptance Tests and Unit Tests as Documents First, Tests Second

    The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]

    kerrick.blog/posts/2025/accept

  4. Acceptance Tests and Unit Tests as Documents First, Tests Second

    The real reason [acceptance tests and unit tests] aren’t redundant is that their primary function is not testing. The fact that they are tests is incidental. Unit tests and acceptance tests are documents first, and tests second. As my wife and I were listening to Uncle Bob's book on professionalism in software, this line surprised me. Maybe it's just because I don't understand tests as well as I'd like, but I had to stop and take note. He clarified exactly what he meant, too: […]

    kerrick.blog/posts/2025/accept

  5. If you code in OOP with the concept of SoC and SOLID you have the possibility to write modern modular classes.

    Take the focus on the testability of the code you write and it will show you the way which you can/must go.

    1. #unittest
    2. #functionaltests
    3. #integrationtests
    4. #apitests
    5. #acceptancetests

    From top to bottom
    From many to few tests

  6. If you code in OOP with the concept of SoC and SOLID you have the possibility to write modern modular classes.

    Take the focus on the testability of the code you write and it will show you the way which you can/must go.

    1. #unittest
    2. #functionaltests
    3. #integrationtests
    4. #apitests
    5. #acceptancetests

    From top to bottom
    From many to few tests

  7. If you code in OOP with the concept of SoC and SOLID you have the possibility to write modern modular classes.

    Take the focus on the testability of the code you write and it will show you the way which you can/must go.

    1. #unittest
    2. #functionaltests
    3. #integrationtests
    4. #apitests
    5. #acceptancetests

    From top to bottom
    From many to few tests

  8. If you code in OOP with the concept of SoC and SOLID you have the possibility to write modern modular classes.

    Take the focus on the testability of the code you write and it will show you the way which you can/must go.

    1. #unittest
    2. #functionaltests
    3. #integrationtests
    4. #apitests
    5. #acceptancetests

    From top to bottom
    From many to few tests

  9. What are the generic patterns and best practices for resetting state of a database, storage, external service, etc, in #AcceptanceTests?

    Or are there any, #lazyweb?