6 Comments
User's avatar
Andre Du Plessis's avatar

Another question on a small detail: Why do you prefer to use the word "driver" for your testing framework directory?

Expand full comment
Markus Oberlehner's avatar

Because I call the specific implementations (Cypress, Vitest, Playwright,...) "drivers".

Expand full comment
Andre Du Plessis's avatar

Markus, you refer to "application tests" when applying Cypress. Are you referring more to E2E tests or Acceptance tests, seeing that Chapter two focussed on Acceptance and Unit tests, but Cypress doesn't use the term "acceptance tests" in their documentation?

I'm referencing your articles of 2018 where you are applying Cypress to do acceptance-like tests:

Part 1: https://markus.oberlehner.net/blog/automated-acceptance-testing-with-cypress-and-vue-setup/

Part 2: https://markus.oberlehner.net/blog/automated-acceptance-testing-with-cypress-and-vue-network-stubs-and-timers/

Expand full comment
Markus Oberlehner's avatar

Sorry for the confusion! I rewrote the first chapters and changed the nomenclature quite a bit. Unfortunately, this is a significant downside of releasing my content as I write it. This will be cleared up in the final version of the book.

Expand full comment
Andre Du Plessis's avatar

I assumed it was due to you possibly rewriting content and you might have started doing so from the beginning, as you indicate in your disclaimers, and not a serious problem for me. I only wanted to confirm with you.

Just to be sure though, the term "acceptance test" as used in your rewritten first chapters would then be the preferred term in contrast to "application tests", correct? (Even though Cypress for example would be using the term "application test", you prefer the, can we say more generic term "acceptance test"?)

Expand full comment
Markus Oberlehner's avatar

The new version uses Application Test exclusively.

Expand full comment