Test Automation

6 Best Practices with Integration Testing in CI Environments: TechBeacon

https://techbeacon.com/6-best-practices-integration-testing-ci-environment
Develop Integration Tests First as they are better suited to catch problems INTRODUCED
Then Unit tests as they are better suited to verify a system INITIALLY, then FIND the source of NEW problems

Integration first, until the fail
Then run Unit Tests to ID source
When Unit Tests pass again
Run Integration Tests
Bounce between the two until both are passing

TestAutomation: Initial Thoughts

Needs to accept plug-able test modules by way of TestBase variations that server as the foundation of the test automation solution
- TestBase could be the SuperClass for the following, provided it has a flexible interface implementation to conveniently draw upon various frameworks for API & Web Browser testing
- PomBase
- ApiBase
  - WSDL
  - REST
- DataBase
- BDDBase
- TDDBase
- SelfCheckBase
Testing Types
- https://www.testingexcellence.com/types-of-software-testing-complete-list/
TestAutomation Thoughts
- https://www.thoughtworks.com/insights/blog/guide-test-automation

TestAuto: DZone on Test Automation Design Patterns

https://dzone.com/articles/design-patterns-in-automation-testing
- Open Close Principle
- SOLID

In most cases, I believe that the best approach to validate taxes and similar money amounts is to call the real production web services that are used to power the actual e-commerce module. They should be already entirely tested via unit and integration tests, and their output should be guaranteed.

6 Best Practices with Integration Testing in CI Environments: TechBeacon

TestAutomation: Initial Thoughts

TestAuto: DZone on Test Automation Design Patterns

Search