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

When running a test suite, only first test gets converted to AppMap #356

Closed
gonzric1 opened this issue Apr 4, 2024 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@gonzric1
Copy link

gonzric1 commented Apr 4, 2024

Expected Behavior: When I run all tests in a file with many tests, all tests return an appmap accessible via the VSCode/Intellij interface.

Actual Behavior: Only first test in file generates an appmap.

When running tests on a file with many tests, all of the files get recorded as a #{test_name}.appmap.json file, but only the first test in each file gets converted to a folder and shows up in the appmap extension.

This seems to happen consistently with controller specs, but not with model specs.

You can get around this by running each test case individually. However, if I try running all tests in a folder, only the first it... statement in each file creates an appmap.

@kgilpin
Copy link
Contributor

kgilpin commented Apr 4, 2024

Hi, can you provide your Ruby version and RSpec version? Maybe rspec has changed in a way that’s outside of our test matrix.

@kgilpin kgilpin added the bug Something isn't working label Apr 4, 2024
@gonzric1
Copy link
Author

gonzric1 commented Apr 4, 2024

ruby '3.2.2'
'rspec-rails', '5.1.1'

@kgilpin
Copy link
Contributor

kgilpin commented Apr 4, 2024

Related: getappmap/appmap-js#1704

should allow the AppMaps to load regardless of stray “returns”.

It seems that something in the test environment of this project (the project that is exhibiting this problem when running specs) is maybe a long running thread that’s producing random call events.

@kgilpin kgilpin closed this as completed Jul 30, 2024
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

No branches or pull requests

2 participants