Code by Sam Pearson.
Day 3 was about learning the different ways that tests can be grouped and selected for running.
At a glance everything was going great. I ran the tests in UI mode, immediately identified that I had missed a ".click()" on one of the tests, fixed it, ran it again.
I started suspecting resource constraints, so I limited the test to one simultaneous worker, like so:
...
In a backend I built for a webapp, the database has model/service/repo layers. The repository layer was meant to have some built-in security.
We still need that pattern of using a getter to check if the entity exists, and in fact I think we're going to have to use it both at the repo layer and at the service layer.
...
A CRUD todo app with full-stack implementation, demonstrating architecture and testing principles.
Test case demonstrations for common webpage features.
An automated API testing framework (includes basic target API and test suite).
Email: sam@ocelotcodesystems.com
GitHub: @SamPearson
LinkedIn: in/samedpearson