-
Notifications
You must be signed in to change notification settings - Fork 103
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
TCK updates for Servlet 6.0 #773
Conversation
The "Ensure passed flag is correctly set on test failure" needs to be back-ported. |
Thanks Mark for working on this, very much appreciated! |
This PR is now at the point where a compliant Servlet 6.0 implementation should pass it. What is missing is new tests for new features. |
d9c26f4
to
6c3ecd0
Compare
Just a rebase. No functional changes. |
@markt-asf - For readers of commit history, we can squash 17 commits of the PR. Also can we requested Servlet SPEC team to review the PR? |
I'd prefer that the commits weren't squashed into a single commit. Obviously you have my +1 to these changes. I've asked on the servlet dev list for other committers to comment here. |
Please add any volunteers from servlet-dev list as reviewer of the PR. |
@markt-asf - Please assign volunteers from servlet-dev for review. |
I asked for additional review volunteers on servlet-dev. No-one stepped forward. |
Should the |
Possibly. Does any actually use the assertion information? I'm wondering if we should continue to maintain it or just remove it entirely. |
Asking only because it was updated in this PR but for other than |
Is fixing #736 related to this PR? |
@markt-asf According to https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/servlet/spec/serverpush/README.md:
The servetpush test seems to still work on Java 17 (from WildFly testing with EE 9.1) but from the serverpush/README/md it sounds like lib/http.jar could be removed and the serverpush test changed to use the java.net.http package since EE 10 will require Java 11+ to run TCKs. I guess that doesn't have to be tied to this pr for Servlet 6.0 specific changes but it could. |
@scottmarlow Now I remember the hack referenced in #736. If we can get rid of this hack then that would be a good thing. I'll take a look today. |
The PR amended the test to accept a 401 or 404
It was never excluded at the Servlet level and the test passes for Tomact 10.1.x so the assumption is that the test is valid.
The Servlet spec and APi has been updated in Servlet 6.0 to refer exclusively to RFC 6265.
The test used comment to pass data. Comment is now a NO-OP so it can't be used going forwards. The use of comment has been replaced with a ServletContext attribute.
A number of tests issue RFC 2109 cookies. The tests have only been updated to process these as per RFC 6265 which essentially means that the attributes such as $Domain get treated as separate cookies.
Changes due to jakartaee/servlet#105
Changes due to jakartaee/servlet#377
6efeabe
to
6a1a344
Compare
I re-based the PR and added a commit to fix #736. |
name: Pull Request
about: Create a pull request for a Platform TCK change
title: 'Servlet 6.0 TCK updates'
labels: ''
assignees: ''
Fixes Issue
None
Related Issue(s)
None
Describe the change
Updates required to the Servlet TCK for the Servlet 6.0 release. Includes some commits that need to be back-ported to earlier TCK versions.
Additional context
None
CC @alwin-joseph @anajosep @arjantijms @cesarhernandezgt @dblevins @m0mus @edbratt @gurunrao @jansupol @jgallimore @kazumura @kwsutter @LanceAndersen @bhatpmk @RohitKumarJain @shighbar @gthoman @brideck @scottmarlow