-
Notifications
You must be signed in to change notification settings - Fork 20
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
fix: Error not showing in failed test result flyout #233
fix: Error not showing in failed test result flyout #233
Conversation
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.
Oops. My bad. thanks for fixing it so quickly 👍
No blame, just forgive me the next 100 times I do something similar 😆 I actually want to add some tests to prevent this problem happening again. I suppose I can merge the fix here and then add them in a follow-up though as we definitely want to get this in before our next release. |
Issue to add tests: #235. |
…-report * upstream/main: fix: Refresh action title on update (elastic#237) feat: Add a controller class for browser process requests (elastic#241) fix: Do not generate code when wrong data is passed or when unnecessary (elastic#239) 0.0.1-alpha.4 fix: Hoist page objects in generated code (elastic#211) Fix bug issue. (elastic#233) chore: Move `createAction` test helpers to top level of repo (elastic#231) ci: refactor the docker build stage (elastic#227) Add status indicator to assertion elements. (elastic#226) ci: report test results (elastic#223) chore: convert electron js to ts (elastic#205)
Summary
Fixes a defect we introduced recently as part of the backend transition from pure JS to TypeScript. I'm going to add tests for this function so we don't fail to notice things like this in the future.
Before
After
Implementation details
We simply forgot to include an optional field in the response from the test procedure.
How to validate this change
Run a journey that you expect to fail, and observe the code/data info in the test result flyout.