Skip to content
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

Closed
3 tasks done
kdhamric opened this issue Jun 8, 2023 · 11 comments
Closed
3 tasks done
Assignees
Labels

Comments

@kdhamric
Copy link
Collaborator

kdhamric commented Jun 8, 2023

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

  1. frontend
    xoscar
  2. xoscar
  3. frontend
    xoscar
@kdhamric kdhamric added feature request triage requires triage labels Jun 8, 2023
@kdhamric kdhamric added epic Epic design and removed feature request triage requires triage labels Jun 8, 2023
@olha23
Copy link

olha23 commented Jun 12, 2023

@kdhamric Should we add ability to make the yaml editable what we discussed in slack channel ?

@kdhamric
Copy link
Collaborator Author

I might tend to 'hold off' on us doing this part until a bit later. For now, lets just show it.

@olha23
Copy link

olha23 commented Jun 13, 2023

@kdhamric do you have AC for REST screen?

@kdhamric
Copy link
Collaborator Author

No - see AC15: Implement REST based means to run test #2707 (waiting on tests migration to resource #2335 )

We need to wait until our API for running a test is updated.

@kdhamric
Copy link
Collaborator Author

We should try to get the CLI and CI/CD coded and released... then we can continue adding to it.

@xoscar xoscar changed the title [Deployment Tab] Epic for adding a fourth tab to Tracetest for automation / running of tests [Deployment Tab] Fourth tab to Tracetest for automation / running of tests Jun 16, 2023
@xoscar
Copy link
Collaborator

xoscar commented Jun 16, 2023

@olha23 I think we are missing to define a couple of things:

  1. The loading state for this tab (what happens when the test run is not in a finished state)
  2. The error page for this tab (when the test fails at trigger o trace steps)

@olha23
Copy link

olha23 commented Jun 19, 2023

@xoscar totally make sense, working on it

@kdhamric
Copy link
Collaborator Author

@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.

@olha23
Copy link

olha23 commented Jun 19, 2023

ok, so if we can run even when test failing, we need add only loading state for this tab ? @xoscar ?

@xoscar
Copy link
Collaborator

xoscar commented Jun 19, 2023

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants