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

typed: Remove extra call to current-test-case-around #133

Closed
wants to merge 1 commit into from

Conversation

jessealama
Copy link
Sponsor

@jessealama jessealama commented Jan 31, 2021

It's not necessary to wrap a test case in current-test-case-around; that will be done later. Doing so increments the running test count (and, possibly, the running test failure count) twice.

The proposed change may seem implausible on its face. I also feel somewhat less than confident that this is the right thing to do. But I can confirm that this does the job.

closes #132

It's not necessary to wrap a test case in
`current-test-case-around`; that will be done later. Doing
so increments the running test count (and, possibly, the
running test failure count) twice.

closes racket#132
@jessealama jessealama changed the title typed: Remove redundant call to current-test-case-around typed: Remove extra call to current-test-case-around Jan 31, 2021
@jackfirth
Copy link
Sponsor Collaborator

I think the problem isn't that this macro expands to a use of current-test-case-around, I think it's that it tries to expand to current-test-case-around and also do the test result logging at the same time. Instead of removing the current-test-case-around usage, I think we should update this code to use roughly the same implementation strategy that the untyped macros use.

@jessealama jessealama closed this Feb 2, 2022
@jessealama jessealama deleted the issues/132 branch February 2, 2022 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect test counting in typed/rackunit (test count doubled)
2 participants