Please enable JavaScript.
Coggle requires JavaScript to display documents.
Introduction to MedMined Automated Testing (Limitations with Automated…
Introduction to MedMined Automated Testing
Current Setup
UI Regression Tests
Selenium Test Framework
WebDriver
Natively 'drive' a web page via code.
Browser Based Web Application Testing Framework
ETTC
Execute tests in Parallel
Smart execution
Push results back into TFS
Expandable
CI friendly
Creates video of test execution
Flexible
Workflow tests
Not very stable
API testing
New - Currently only testing Phoenix Reporting
testing an API directly makes it easier to isolate errors in the back end.
A part of CI - executed nightly
Greater confidence in data
Golden DataSet Required
Tests are short - Each tests usually tests one thing
Plans For the Future
Near Term
Add UI Smoke Tests to CI
Manual Testers will start testing APIs.
Evaluate if any of them can help with coding of these tests
Start integrating API's into UI tests
Reduce test time
Increase stability
Long Term
Increase stability of tests
Improve integration of automated testing during sprints
Add Entire Automated Regression Suite to CI
Continue to reduce test run times
Limitations with Automated Testing
False sense of quality
Not reliable/stability issues
Automation is not testing
Maintenance Time and Effort
Slow feedback
Not many bugs found
Benefits of Automated Testing
Confirmation of the known
Quick feedback
Fast execution of checks
Frees up the time of the testers
What can be automated?