Design test suite
Estimation
Story points : 3 SP
Estimated Duration: 4 Days
Summary
Description
We need a plan that we can execute constantly on the current infrastructure as well as on new realeases as they are deployed to test, staging and production. In general, we should aim towards all of the tests being automated to expedite testing and give us a report for each release / current status performance. We will also have to complete some manual tests that test the latest functionality we have delivered in a release.
Why is this feature important?
We need to expedite testing to understand any breaking changes or performance issues we introduce through code changes.
Work Breakdown Structure (WBS)
| Task | Description | Duration | Status | Start Date | End Date | Comment |
|---|---|---|---|---|---|---|
| 1 | Identify and write-down the installation test case in end user's perspective | 1D | Done | 06 Oct 23 | 09 Oct 23 | |
| 2 | Identify and write-down the device onboarding test cases in end user's perspective | 1D | Done | 10 Oct 23 | 10 Oct 23 | |
| 3 | Identify and write-down the ML job scheduling test cases on SPD application in end user's perspective | 1D | To Do | |||
| 4 | Identify and write-down claiming a job test cases on CPD in end user's perspective | 1D | To Do | |||
| 5 | Identify the framework to automated the test cases | |||||
| ------ | ------ | ------ | ------ | ------ |
Edited by Abhishek Shukla