Test Automation  -               Continuous Improvements

Get Started. It's Free
or sign up with your email address
Rocket clouds
Test Automation  -               Continuous Improvements by Mind Map: Test Automation  -               Continuous Improvements

1. CI and CD

1.1. Plan Branches

1.1.1. MAIN branch, which is the GOTO production like copy

1.1.2.  Strategy of retiring development branches when projects conclude

1.1.3. avoid duplication and better collaborated coding / automation

1.2. SVN

1.2.1. • Absolutely, no check-ins policy without reviews

1.2.2. • Always ensures checked-in code in SourceControl builds and is executable on demand

1.3. Daily Runs

1.3.1.  Keeping it current (Making people trust (and rely on) results from the automated tests)

1.4. Make it part of definition of DONE.

2. Coding Standards

2.1. Peer Reviews

2.1.1.  before check-ins

2.1.2. Absolutely, no check-ins policy without reviews

2.2. Exception Handling

2.3. Error Logging

2.4. Documentation

2.4.1. • Requirements covered by a test, and up to what point (a date) • What is too little or too much, being meaningful in generic comments • Comments describing special needs of the test or performance implications or external interface requirements • Data requirements if its trivial

2.5. Naming Conventions

2.5.1. • Tests, support / framework Classes, Methods, Properties etc

2.6. Design techniques

3. Tools Consolidation

3.1. o Evaluation and association of new software libraries /techniques

3.1.1.  Could be an Assertion library  Could be a the next new version Selenium…. Etc….

4. Reports and Status

4.1. Aggregated Test Results

4.2. Frequency Of Test Execution

4.3. Reusability

4.4. Complexity

4.4.1. Technical Feasibility

4.5. Execution Time

4.6. Automation Coverage

4.7. o ROI for Automation

5. Test Mangement

5.1. Clean-up

5.2. Xray Utilities

5.3. One-Click Quarantine

5.3.1. Isolate tests that need maintenance

5.4. Agree on Definition of DONE

5.5. The review / sign-off process

5.5.1.  Who the sign-off is obtained from (Viz BAs, Architects, DB Developers, UI Developers, Integration Developers etc.)

5.5.2.  For which artefacts is the sign-off required …. Maybe perhaps just the BDD, to ensure

5.5.2.1. • Business coverage is achieved • Any special requirements that need focussing is captured and validated • Adequate boundary testing is achieved etc

5.6. Who makes tests current

5.6.1. Automated?

6. UpSkilling

6.1. Web

6.2. Integration

6.3. Thick Client

6.4. Mobile

6.4.1. Responsive Web

6.4.2. Apps

6.5. Shell Scripting

6.6. o On boarding process (for new starters)

7. Frameworks

7.1. Function/Module Script Reusability

7.2. Ease Of Use

7.3. Report Customization

7.4. Maintainance

7.4.1. BUG fixes (Production Systems as well as Automated Frameworks / Tests)

7.5. Integration with other tools

7.6. Alignment to SPF

7.7. o SMEs and ownership of certain platforms (automation frameworks)

8. Automation Standards

8.1. BDD Principles

8.2. Fully Automated Regression Suites

8.3. Code to the Requirements - Prioritize

8.4. 20-30-50% GUI-API/Integration-Unit