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

FeatureTestCaseTest still broken #1446

Closed
jim-parry opened this issue Nov 9, 2018 · 1 comment · Fixed by #1468
Closed

FeatureTestCaseTest still broken #1446

jim-parry opened this issue Nov 9, 2018 · 1 comment · Fixed by #1468

Comments

@jim-parry
Copy link
Contributor

This was resolved(?) in #1242?
there are still seven "risky" tests reported :(

1) FeatureTestCaseTest::testCallGet
Test code or tested code did not (only) close its own output buffers
2) FeatureTestCaseTest::testCallSimpleGet
Test code or tested code did not (only) close its own output buffers
3) FeatureTestCaseTest::testCallPost
Test code or tested code did not (only) close its own output buffers
4) FeatureTestCaseTest::testCallPut
Test code or tested code did not (only) close its own output buffers
5) FeatureTestCaseTest::testCallPatch
Test code or tested code did not (only) close its own output buffers
6) FeatureTestCaseTest::testCallOptions
Test code or tested code did not (only) close its own output buffers
7) FeatureTestCaseTest::testCallDelete
Test code or tested code did not (only) close its own output buffers

@jim-parry jim-parry added this to the 4.0.0-alpha milestone Nov 9, 2018
@puschie286
Copy link
Contributor

very hidden error : commit 0cc5b7d changed the underlying "call" method and this doesn't work for derived classes

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 a pull request may close this issue.

2 participants