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

fix: Error not showing in failed test result flyout #233

Merged

Conversation

justinkambic
Copy link
Contributor

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

image

After

image

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.

@justinkambic justinkambic added the bug Something isn't working label Apr 28, 2022
@justinkambic justinkambic requested a review from kyungeunni April 28, 2022 19:19
@justinkambic justinkambic self-assigned this Apr 28, 2022
@apmmachine
Copy link
Contributor

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-04-28T19:19:45.890+0000

  • Duration: 9 min 2 sec

Test stats 🧪

Test Results
Failed 0
Passed 66
Skipped 0
Total 66

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

Copy link
Contributor

@kyungeunni kyungeunni left a 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 👍

@justinkambic
Copy link
Contributor Author

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.

@justinkambic
Copy link
Contributor Author

Issue to add tests: #235.

@justinkambic justinkambic merged commit c8f071a into elastic:main Apr 29, 2022
@justinkambic justinkambic deleted the 232/include-error-in-ipc-response branch April 29, 2022 16:13
v1v added a commit to v1v/synthetics-recorder that referenced this pull request May 11, 2022
…-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)
@shahzad31
Copy link
Contributor

POST FF Testing LGTM

it shows an error
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants