-
Notifications
You must be signed in to change notification settings - Fork 18
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
STU-270 | Test Sequencer: export complexe data type produced in test #1118
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
May as well add a docs page in this PR so we don't have to refer back to this video for a how-to. Maybe upload this video to youtube (unlisted) and embed it in the docs? Can do that part later.
One question. How does it know the test_id? If you have a test with multiple different test types? |
Yes that's a good idea :) |
Oh wait, did I forgot to handle that, let's me test it. Currently, the Test Sequencer retreive the last data exported with: |
Oh does it just look at the function name and look for the test with that name? |
The test sequencer tells the test where to store the data based on the testName (in the UI).
|
Let's do the docs in another PR, I'll need this feature for a demo this week
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.
lgtm
Demo
Screen.Recording.2024-02-28.at.2.01.37.PM.mov