Testing

Some good articles/discussions on the matter:

• https://www.softwarepragmatism.com/should-i-deploy-test-code-to-production
• https://stackoverflow.com/questions/9022547/should-test-code-be-separate-from-source-production-code
• https://www.softwarepragmatism.com/should-i-deploy-test-code-to-production

• https://www.cigniti.com/services/test-automation/
•  

• https://www.sciencedirect.com/science/article/pii/S1877050914001045
• https://ac.els-cdn.com/S1877050914001045/1-s2.0-S1877050914001045-main.pdf?_tid=a84352f1-815a-486e-b110-974016ac588b&acdnat=1546490940_2a23e5afff645eb289e6c90afa98290f

• https://www.oracle.com/technetwork/articles/entarch/shrivastava-automated-frameworks-1692936.html

Broad Types of Automation Framework

Automation frameworks can be classified according to four broad types, each of which has unique advantages and disadvantages, as shown in Table 1. The choice of a particular type depends upon a wide range of external factors.

• https://www.softwaretestinghelp.com/test-automation-frameworks-selenium-tutorial-20/

Though the above pictorial representation of a framework is self-explanatory we would still highlight a few points.

• 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

• https://trends.google.com/trends/explore?geo=US&q=Typescript%20selenium,javascript%20selenium,php%20selenium,java%20selenium

TypeScript for Web Testing, No Thanks - Check back in 10yrs