Skip to content

Conversation

hetunandu
Copy link
Member

Reopening #3218

@akash-codemonk akash-codemonk requested a review from riodeuno March 5, 2021 11:35
@akash-codemonk akash-codemonk merged commit bc646ab into release Mar 11, 2021
@akash-codemonk akash-codemonk deleted the fix/tab-widget-delete branch March 11, 2021 04:18
sondermanish pushed a commit that referenced this pull request Mar 6, 2024
## Description
UI for showing run history for a workflow. Changelog
- Redux setup for fetching the API (reducer, selectors and actions)
- New API and req + response types for workflow run history fetch and
run details fetch
- Added trigger in the bottom bar of workflow editor to trigger opening
the run history pane
- Added a pane with tabs for workflow run history to open in the main
pane

Please note: since the APIs are not yet merged, opening the tab will
give an error, this should be fixed once the APIs are merged in.

To be added:
- Pagination for workflow run history once the APIs are ready.

#### PR fixes following issue(s)
Fixes [#30357](#30357)
Fixes [#30358](#30358)
Fixes [#30359](#30359)
Fixes [#30360](#30360)
Fixes [#30361](#30361)

#### Media
> A video or a GIF is preferred. when using Loom, don’t embed because it
looks like it’s a GIF. instead, just link to the video
>
>
#### Type of change
> Please delete options that are not relevant.
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- Chore (housekeeping or task changes that don't impact user perception)
- This change requires a documentation update
>
>
>
## Testing
>
#### How Has This Been Tested?
> Please describe the tests that you ran to verify your changes. Also
list any relevant details for your test configuration.
> Delete anything that is not relevant
- [ ] Manual
- [ ] JUnit
- [ ] Jest
- [ ] Cypress
>
>
#### Test Plan
> Add Testsmith test cases links that relate to this PR
>
>
#### Issues raised during DP testing
> Link issues raised during DP testing for better visiblity and tracking
(copy link from comments dropped on this PR)
>
>
>
## Checklist:
#### Dev activity
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] PR is being merged under a feature flag


#### QA activity:
- [ ] [Speedbreak
features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-)
have been covered
- [ ] Test plan covers all impacted features and [areas of
interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-)
- [ ] Test plan has been peer reviewed by project stakeholders and other
QA members
- [ ] Manually tested functionality on DP
- [ ] We had an implementation alignment call with stakeholders post QA
Round 2
- [ ] Cypress test cases have been added and approved by SDET/manual QA
- [ ] Added `Test Plan Approved` label after Cypress tests were reviewed
- [ ] Added `Test Plan Approved` label after JUnit tests were reviewed

---------

Co-authored-by: Hetu Nandu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants