You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there are two ways of mapping request events to servlet requests. The classic way is covered by tests using com.amazonaws.serverless.proxy.internal.testutils.AwsProxyRequestBuilder, the new way using Spring Cloud is tested in com.amazonaws.serverless.proxy.spring.AwsSpringHttpProcessingUtilsTests. The latter doesn't cover all cases that were already implemented in previous years, so we'd need to transfer the tests.
Currently there are two ways of mapping request events to servlet requests. The classic way is covered by tests using
com.amazonaws.serverless.proxy.internal.testutils.AwsProxyRequestBuilder
, the new way using Spring Cloud is tested incom.amazonaws.serverless.proxy.spring.AwsSpringHttpProcessingUtilsTests
. The latter doesn't cover all cases that were already implemented in previous years, so we'd need to transfer the tests.Ideally we'd leverage the official TCK https://github.com/jakartaee/servlet/tree/master/tck to some extend.
The text was updated successfully, but these errors were encountered: