A better Trader testing: Difference between revisions
(→Intro) |
No edit summary |
||
| Line 9: | Line 9: | ||
Testers will focus on the website and iPhone app. Testing is managed on the project boards. | Testers will focus on the website and iPhone app. Testing is managed on the project boards. | ||
== Project Boards == | === Project Boards === | ||
Each test task is represented by a "ticket" on a "board". | |||
Initially the ticket is created with a description of the tests that are needed. As you test, you will capture all the details of the tests in the ticket, including screenshots, whether the test passed, and all other details. | |||
The tickets on the boards will generally flow from left to right as the status changes: | |||
Open > Sprint > In progress > Failed > Ready For Testing > Testing > Ready For Release > Done (released) | |||
* [https://shitcutter.com/the-digital-age/a-better-trader/frontend/atui/-/boards/21 Website board] | * [https://shitcutter.com/the-digital-age/a-better-trader/frontend/atui/-/boards/21 Website board] | ||
* [https://shitcutter.com/the-digital-age/a-better-trader/frontend/ios/abettertrader/-/boards/18 iPhone app board] | * [https://shitcutter.com/the-digital-age/a-better-trader/frontend/ios/abettertrader/-/boards/18 iPhone app board] | ||
* [https://shitcutter.com/the-digital-age/a-better-trader/server/-/boards/9 Server board] | * [https://shitcutter.com/the-digital-age/a-better-trader/server/-/boards/9 Server board] | ||
Revision as of 03:00, 12 March 2024
Intro
This page introduces the app to members of the test team, and explains the basics of performing testing.
Projects
There are two ways to get to the app, either via the website or the iPhone app (installed and updated via the TestFlight app). Both need testing separately from each other. In addition, there is a server that works behind the scenes. This is mostly tested automatically through tests written by the developers.
Testers will focus on the website and iPhone app. Testing is managed on the project boards.
Project Boards
Each test task is represented by a "ticket" on a "board".
Initially the ticket is created with a description of the tests that are needed. As you test, you will capture all the details of the tests in the ticket, including screenshots, whether the test passed, and all other details.
The tickets on the boards will generally flow from left to right as the status changes:
Open > Sprint > In progress > Failed > Ready For Testing > Testing > Ready For Release > Done (released)