Defects in Sub-tasks
- Mike Deskis
- Ioana Kocurova
Some of the PMs or customers don’t want to have bugs reported as “BUG” as they report it this way themselves. In such case there is possibility to report bugs as sub-task.
What defect
creating bugs in sub-tasks instead of BUG types
Why test a defect
Sub-tasks with a defect for better defect handling between QA analyst and configuration engineer.
Approach made work for developers easier. They can fix defect after they will have time and not jump from one think to another. Approach for not losing context of found issues.
Where to test defects
create sub-task under original task/user story
How to test defects
Open original user story where you want to create a sub-task, write a short description of the sub-task and save.
When the sub-task is created following information needs to be filled:
Description - should be as much detailed as possible. Might contain printscreens, steps how to reproduce the issue
Assignee - assign the bug to the developer immediately
Label - not required however it helps you to filter all your bugs when needed
Example Testing
Expert Price is Missing
Expert price is missing when there are more records in one Price list and there is no “No” in active CPQ column. it happens when the records belong to the same date range. Logic does not know which record should be chosen.
Refer to contract C-349 and GOV0419 PL in the QA partition.
Not Possible to Add Product Line Item
An issue has been identified where it is not possible to add a product line item to an OE contract. To reproduce this issue, users can create an OE contract and attempt to add a Retreat Michelin line item, which will result in no product line being added. This same issue has also been observed for GPR contracts, and the problem can be replicated using C-309. (you can read more about it below)
→ You can test an issue where GPR and OE always delete all the line items upon recalculation due to a bug in the header logic.
The intended behavior is for only the groups and subgroups to be deleted, while the product lines should remain as required.
Additionally, an overlooked scenario involves the default Bid type for GOV accounts being GSGU, which correctly generates the groups.
However, if the user selects GPR instead, it clears the contract off of all the group entries upon recalculation. Furthermore, in the event that a user changes their selection to GSGU or DGGU contract type, the default CPQ product groups should be added again upon recalculation, which is currently not captured and requires reporting in order to be fixed.
NOTES:
Not for all defects were created sub-tasks. Some of the defect were handled immediately with developers or in comments.
Defects are possible to manage in sub-tasks (report). When defects are written in comments it is not possible to do it.
logging bugs as bugs or sub-task is important to keep track of the ongoing issues which are easily lost in comments
In case there are also sub-tasks created for recording test results there might be kept some differentiation in description already (e.g. write BUG on the beginning of every description, see examples above)