-
Notifications
You must be signed in to change notification settings - Fork 73
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
[Deployment Tab] Fourth tab to Tracetest for automation / running of tests #2693
Comments
@kdhamric Should we add ability to make the yaml editable what we discussed in slack channel ? |
I might tend to 'hold off' on us doing this part until a bit later. For now, lets just show it. |
@kdhamric do you have AC for REST screen? |
We should try to get the CLI and CI/CD coded and released... then we can continue adding to it. |
@olha23 I think we are missing to define a couple of things:
|
@xoscar totally make sense, working on it |
@xoscar @olha23 I would expect 'how to run' to be totally separate from 'it is running successfully (or not).' The 'how to run' is very much a definition, similar to the trigger definition and the test definition. Even for a failing test, you should still be able to grab the definition and how to run it. Am I thinking about it wrong? We may need to handle people copying the definition for a test that is not saved yet... but we can likely handle that in v2 if it is an issue. |
ok, so if we can run even when test failing, we need add only loading state for this tab ? @xoscar ? |
@olha23 I think we dont, we can have it all available from the get-go for the first version and decide if we want to keep it that way or change it afterward |
As a user, my process in Tracetest is to create a trigger, look at and improve the trace, build tests... and then automate the tests as part of my CI/CD process. We want to add a fourth tab to contain this functionality.
Tasks
The text was updated successfully, but these errors were encountered: