@@ -52,7 +52,9 @@ Regressions are changes that damage existing functionality. Testing for regresio
#### New Feature Acceptance Testing
New Feature testing is preformed by developers writing unit tests on new features and interacting with new features in local development environments and development instances. It is also preformed by stakeholders behind feature flags. And a final layer of new feature acceptance testing is performed by canary users.
New Feature testing is preformed by developers writing unit tests on new features and interacting with new features in local development environments and development instances. It is also preformed by stakeholders behind feature flags. And a final layer of new feature acceptance testing is performed by canary users.
Feature flags, staging environment and canary user flag are used effectively to test new features.
### Proposed Modifications
...
...
@@ -79,9 +81,32 @@ Mobile automated E2E tests coverage should be maintained as cypress test are mai
#### New Feature Acceptance Testing
The primary limiting factor on our New Feature acceptance testing has been a lack of detailed wireframes and specifications. Wireframes and specifications are needed to create the standard a new feature is being tested against.
The primary limiting factor on our New Feature acceptance testing has been a lack of detailed wireframes and specifications. Wireframes and specifications are needed to create the standard a new feature is being tested against. This should be better now that we have Michael to create specifications and wireframes.
Ubertesters can be employed every couple of Sprints (bi-sprintly, once in a fortsprint) to run a test cycle.
- ubertesters are best used when given specific instructions of what to test
- Xander can cooridinate with ubertesters after discussing feature specifications with Michael and stakeholders
- Xander can then create a test plan with ubertester project manager Tanya
- Xander should be able to set up testers with tools to perform task eg. tokens, dumby credit card
- Xander can migrate and triage results from ubertester platform to gitlab
#### UX Testing
UX Testing, I strongly believe some of the easiest gains for us in user retention are in UX improvements. I believe we should pilot a User Experience testing service like [User Brain](https://userbrain.net/) and provide the results to Michael.
- I have investegated using Ubertesters for this kind of service and concluded that they are simply not setup to provide User Experience Testing services.
- testers don't have great English language skills
- testers aren't set up for video capture
- no supporting platform, we would have to manage captured video
- If we captured video of users try and complete simple tasks in Minds many of the easy to fix wrinkles in the UX will become apparent.
#### Service (Model/Controller) Testing
While we have good unit test coverage however we have no service level testing of our API engine. Robust testing of our API end points will improve quality and better allow us to isolate problems to the engine. It will also facilitate documenting our engine/API for other open source organizations who wish to adopt our code.
Responsibility for service level testing could be considered a developer responsibliity or a QA responsibility because it could be considered E2E testing for the engine repository.
An API testing tool popular with the development team is [Postman](https://www.getpostman.com/)
