Automated Acceptance Test Framework

Get Started. It's Free
or sign up with your email address
Automated Acceptance Test Framework by Mind Map: Automated Acceptance Test Framework

1. Robust tests - not brittle on implementation details

2. Devices

2.1. Testing on a Single Device

2.2. Concurrent tests on devices

2.3. Sequential tests on devices

2.4. Automated Test Run on all devices upon build request

2.5. Tablet Support

2.6. Web App Support

2.7. Testing on different Applicaitons on multiple devices

2.8. Testing on multiple browsers

2.9. Emulators for all devices that cannot be rigged up.

2.10. Emulators for all devices and OS versions as standard before tests are pushed to hardware devices

3. Risk based testing (ACC style?)

3.1. Risk analysis method

3.1.1. Dividing test suite into different risk profile levels for selective running?

3.1.2. Attributes, Components, Capabilities

3.2. Integrating exploratory testing with automated testing

4. Hardware Solution

4.1. New USB Hubs - check they are fit for purpose

4.2. Order new Micro USB to USB cables

4.3. Secure Mac mini to TV/Desk

4.4. Physical Display Solution for Test Run Results

4.5. Build / Order a suitable rack for devices

5. Software Solution

5.1. Framework

5.1.1. Software Framework to allow tests to run (which Software?) Jasmine? Gherkin / Cucumber? Concordion? Twist? SpecFlow?

5.1.2. Application Deployment method / Re-deployment method

5.1.3. Results History / Report Failures

5.1.4. Dashboard for Results Bamboo? Custom Webpage? Sonar? Geckoboard?

5.1.5. Reporting Tool / Mechanism Bamboo? Sonar?

5.1.6. Shared location to store tests Bamboo? Jenkins

5.1.7. Different Test Suites can all be run via the framework Unit Tests Performance Tests UI Tests Integrated Tests Acceptance Tests

6. End User Interaction

6.1. QA Manager / QA Team able to script automated UI tests (we need a DSL that lends itself to being used by the man in the street

6.1.1. Ability to easily refactor test instrumentation

6.1.2. Regression tests should be in same form

6.2. Red Siren of Warning!!

6.3. Radiator of projects showing build status

6.3.1. Give the PO/BA a quick way to know what the acceptance status of every project they work on is, and make that visible across the team

6.3.2. Give the PO/BA a quick way to drill down and find out what's been happening so they can prioritise with all the facts


7. Links to Other Frameworks

7.1. Dovetail with Continuous Integration Process

7.2. Dovetail with Continuous Delivery Pocess

7.3. Dovetail with Code Review Process

7.4. Dovetail with Code Quality Metrics

8. Documentation

8.1. Document the whole Software Framework process on the Wiki

8.2. Document Hardware setup process on the Wiki

8.3. Review and test documentation prior to launch

9. Project Management

9.1. New JIRA Project

9.2. Resource Allocated

9.3. Project Team Mobilisation

9.4. Scope / Costs / Benefits Mapped

9.5. Requirements Analysed (Canvas Opinion from the Team)

10. Outsource our Testing

10.1. Crowd Testing

10.2. UTest

10.3. Consultancy (ie Sopra, 2i, Edge etc)

10.4. Specialist Contractors (ie Sopra, 2i, Edge etc)

10.5. Near-shore

10.6. Off-shore

11. Types of Tests

11.1. Database Tests

11.2. Abstract Layer

11.3. UI

11.4. Model Layer

11.5. Screenshot comparisons