LLM exception suggestion front end #545
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DexterDreeeam
requested review from
lifesaver0129 and
olivershen-wow
as code owners
hydraxman
reviewed
Jul 24, 2023
| { | ||
| suggestions.length > 0 ? | ||
| <AdaptivePropertyTable properties={suggestions} | ||
| title='LLM Suggestions' |
There was a problem hiding this comment.
Suggested change
| title='LLM Suggestions' | |
| title='Test Result Analysis' |
There was a problem hiding this comment.
We can generalize this in user interface, no need to mention the solution LLM behind it.
|
@DexterDreeeam please complete the PR description and attach the screenshot of the feature in it, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LLM exception analyze suggetion in Front end.
Description
Add a component in Test Case UI page to show LLM exception analyze suggestion.
Linked GitHub issue ID:
Pull Request Checklist
Does this introduce a breaking change?
If this introduces a breaking change for Hydra Lab users, please describe the impact and migration path.
How you tested it
Please make sure the change is tested, you can test it by adding UTs, do local test and share the screenshots, etc.
Please check the type of change your PR introduces:
Feature UI screenshots or Technical design diagrams
If this is a relatively large or complex change, kick it off by drawing the tech design with PlantUML and explaining why you chose the solution you did and what alternatives you considered, etc...