Testing
Approach
- Manual : positive + negative + flow test cases (N build)
- Automation : flow test cases (N-1 build)
- Future : Test Driven Development Approach Sample test cases
Automation Tools
- Automation testing = Mimic user (UI) functional testing (+ cross browser testing?)
- Front end code is written in HTML5 standards so it supports all modern browsers like Chrome, Firefox, Edge, Opera...
- Using some build tool & polyfills we can support old browsers like IE11.
| Library/ tool | Browsers | Language | Comments |
|---|---|---|---|
| Google puppeteer | Chromium (Chrome, Edge, Opera) headless, now firefox & screen emulation available | javascript | Build tool handles IE11, still IE11 must be visualized manually. ((rich community) ) |
| Microsoft playwright | Chromium (Chrome, Edge, Opera) headless, firefox, Emulate Responsive screens | javascript | Build tool handles IE11, still IE11 must be visualized manually. (smaller community from puppeteer team 0.9 version) |
| Selenium | Chromium driver (Chrome, Edge, Opera) headless + IE driver + Firefox driver | Java/ javascript | Separate code for firefox & IE11 (rich community) |
| TestCafe | Chrome, Edge, Opera, IE11, Firefox | javascript | No browser plugins (NodeJS) (smaller community as new) |
Note: phantomJS + Casper JS (deprecated as browser feature provided)
Accessibility automation testing //check alternative
puppeteer with protractor //similarly use aurelia e2e testing
API Testing
- Manual testing by POSTMAN UI
- Automation testing by JEST + (newman/ superTest)
- write in generic way like postman config (ecen testing people should use without knowledge)
- JestAndSuperTest Example
- From cli can run particular file/ folder/ all
- Few parallel new man
- More parallel new man issue
- stats & logs of testing
Unit Testing
- (fb)Jest/ Jasmine | the intern |
Performance testing
Check Performance.md
Security testing
check Security.md