TECH DEBT - Implement UI e-2-e automation of Smoke test cases (FAT-552)

[UXPROD-3605] Prokopovych: INVENTORY Smoke e-2-e tests (NFR) - R2 2022 Created: 10/Mar/22  Updated: 08/Jul/22  Resolved: 08/Jul/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Morning Glory (R2 2022)
Parent: TECH DEBT - Implement UI e-2-e automation of Smoke test cases

Type: New Feature Priority: P3
Reporter: Holly Mistlebauer Assignee: Anton Emelianov (Inactive)
Resolution: Done Votes: 0
Labels: NFR, quality_control, tech-debt, ui-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by FAT-822 Implement e-2-e automation of test ca... Closed
Release: Morning Glory (R2 2022)
Epic Link: TECH DEBT - Implement UI e-2-e automation of Smoke test cases
Front End Estimate: XXL < 30 days
Front End Estimator: Holly Mistlebauer
Front-End Confidence factor: 20%
Development Team: Spitfire
PO Rank: 0

 Description   

Prokopovych needs to create end-to-end smoke tests for all of the tests cases identified in Test Rail as "Smoke tests" for our modules.



 Comments   
Comment by Charlotte Whitt [ 29/Jun/22 ]

Hi Anton Emelianov and Holly Mistlebauer - I had a call with the QA test writer Yekaterina Kim yesterday re. TestRail case C3506
Catalog a new title which has been ordered and received in Orders - https://foliotest.testrail.io/index.php?/cases/view/3506

And this work is associated at the only FAT ticket to this given feature UXPROD-3605 Closed .
And here to my question - where I'm getting really confused - how can this QA test writing work be estimated to be XXL < 30 days?

CC: Oleksii Petrenko

Comment by Magda Zacharska [ 06/Jul/22 ]

Moving to Spitfire team as the only ticket associated with this feature is being assigned to the Spitfire team

Generated at Fri Feb 09 00:33:21 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.