-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
workflow_detail unit tests #345
Conversation
Signed-off-by: saimedhi <[email protected]>
Signed-off-by: saimedhi <[email protected]>
Signed-off-by: saimedhi <[email protected]>
workflow_detail tests
Signed-off-by: saimedhi <[email protected]>
workflow_detail tests
Signed-off-by: saimedhi <[email protected]>
Signed-off-by: saimedhi <[email protected]>
workflow_detail tests
Signed-off-by: saimedhi <[email protected]>
workflow_detail tests
return <WorkflowDetail setActionMenu={jest.fn()} {...props} />; | ||
}} | ||
/> | ||
<Redirect from="/" to={`/workflow/${workflowId}`} /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wondering why we need this redirect? Can't we specify the path directly on line 44?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- @ohltyler, Removed Redirect and instead adding initialEntries within the history.
- And also below path should not be removed. Whenever URL matches the below pattern then workflowId will be dynamically obtained from URL. Similar to the actual use case of workflowDetail Component.
path="/workflow/:workflowId"
LGTM on those checks. But to complete the basic UT, we should check any general functionality based on the scope of each component as well. Some things I can think of:
Overall, I'd recommend playing around with each page and trying to cover more basic expectations, besides strictly reading for text fields being visible. You can refer to the detector list test suite in AD for some detailed examples. I don't think we need to start this extreme, but should check that the base functionality is there across the whole page. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These can be covered in a followup PR
Signed-off-by: saimedhi <[email protected]>
workflow_detail tests
* workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> * workflow_detail tests Signed-off-by: saimedhi <[email protected]> --------- Signed-off-by: saimedhi <[email protected]> (cherry picked from commit afb45d6)
Signed-off-by: saimedhi <[email protected]> (cherry picked from commit afb45d6) Co-authored-by: Sai Medhini Reddy Maryada <[email protected]>
Description
Issues Resolved
Related to #95
Check List
--signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.