-
Notifications
You must be signed in to change notification settings - Fork 409
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
Add integration tests progress reporting #3471
Add integration tests progress reporting #3471
Conversation
@rubiagatra please leave a comment at #3055 so it can be assigned to you |
fae6ad6
to
5d66c52
Compare
done @AlekSi! already commented |
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.
Please un-draft it and re-request review once it is ready
5d66c52
to
241cafd
Compare
Hey @AlekSi this is my first iteration sorry for still WIP. Could you check is this going in the right way? The output of the integration should be like this
I know it is not really ready to review but I need your guidance Thank you! |
241cafd
to
668e1bc
Compare
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.
I think the output should be something like that:
Pass: TestCommandsAdministrationServerStatusStress 1/1500
Pass: TestFindCommentMethod 2/1500
…
We could cut github.com/FerretDB/FerretDB/integration
prefix and add current/total output.
668e1bc
to
ff897de
Compare
got it @AlekSi, let me update for it. I'll let you know if it ready |
458dbb0
to
22d28f7
Compare
Hi, @AlekSi I just updated the code It look like this
I know the total tests are not 247 because of nested tests. How we approach these problem? I only can get the root of the test maybe want to sum all test inside integration test?
|
HI @AlekSi, Let me know if something is not right in my implementation at the error / skip test. I resolved all requested changes. Thank you! |
@rubiagatra I updated tests. I think we should include the output of the parent(s) test if subtest fail, so we could read the whole log in one place. On the other hand, if subtest fails, there is no need to show parent test output, I think. And we should add a test where the parent test fails. |
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.
Got it @AlekSi will let you know if its done |
HI @AlekSi Sorry for the late update. I a little bit struggle with this from:
Can you give me an idea of how we do this? Should we collect all the logs first, check which child failed, and log them all in the correct order based on your suggestion? We cannot print directly, as we do now. Thank you! |
@rubiagatra I played a bit with the expected output to make it good enough with a simple implementation – and I think it is good enough now :) Thank you! |
I want to say thank you for your support @AlekSi, I hope I can contribute more in the future! |
Description
Closes #3055 . Still WIP
Readiness checklist (Still in discussion)
task all
, and it passed.@FerretDB/core
), Milestone (Next
), Labels, Project and project's Sprint fields.