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

more tests on the generated code #203

Open
UnquietCode opened this issue Jan 20, 2015 · 1 comment
Open

more tests on the generated code #203

UnquietCode opened this issue Jan 20, 2015 · 1 comment

Comments

@UnquietCode
Copy link
Owner

While the compiled tests are good for execution, it would be nice to perform some static analysis as well. For example, annotation values, parameter types, return types, etc. can all be tested by introspecting the classes in a test and checking for expected values.

@UnquietCode
Copy link
Owner Author

One idea for this is to create an assertion helper which introspects classes inside of the compiled classloader (in-memory compilation), done through the compiled tests harness. The helper could even be fluent and generated by Flapi itself. Something like: assert.that(clazz).method("getName").hasReturnType(String.class)

This is a non-trivial amount of work, and I'm not sure where it would be most useful. Probably then it will have to wait until a significant feature or breakage warrants the investment.

@UnquietCode UnquietCode removed this from the 0.8 milestone Mar 18, 2015
@UnquietCode UnquietCode removed the Task label Mar 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant