-
Notifications
You must be signed in to change notification settings - Fork 2
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
Content Type Check + Leaner Simulator JAR #49
base: master
Are you sure you want to change the base?
Conversation
3bbc943
to
05bc662
Compare
85e2a88
to
bd58252
Compare
5296e5d
to
3fd43f1
Compare
…anyways Pull the nested classes out, such that: 1) We don't have to craft a regex to deal with including RequestResult$TestURIBuilder.class, but still exclude the other tests 2) RequestResult is not so big
Over the weekend, it occurred to me I should diff the JARs just to be sure. and I found some issues that I fixed with more regex's. I ran this with a couple cleanspeak apps and it worked fine, I think this path, although it can work OK, it feels brittle. To me the best way to solve it though may not be attainable right now because it ideally would require multi-module building. We'd need these modules:
To me this would be the only "foolproof" way of ensuring that the simulator JAR ends up with all the right classes in it, even if they are refactored/moved around. We could imitate that with Savant by adding more |
Published simulator JAR, as is, has all the tests for PMVC itself in it as well, which is not needed on other projects. Alternatively, perhaps better, the simulator source could be moved to a different directory so we are not cherry picking with regexes quite as much but that might require more Savant changes.
JSON assertions do not check the content type. It's unlikely it would be wrong, but this ensures it's checked.