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

Introduce a "unit test" extension #780

Closed
6 of 9 tasks
dmlloyd opened this issue Feb 6, 2019 · 4 comments
Closed
6 of 9 tasks

Introduce a "unit test" extension #780

dmlloyd opened this issue Feb 6, 2019 · 4 comments
Assignees
Labels
triage/out-of-date This issue/PR is no longer valid or relevant

Comments

@dmlloyd
Copy link
Member

dmlloyd commented Feb 6, 2019

We need to introduce a fake extension for unit/regression testing the extension mechanism.

  • Introduce the basic extension
  • Exercise all the different config phases
  • Exercise as many config types as possible including lists, maps, & primitives
  • Use bytecode recording in both stages
  • Be compiled & tested with Javac and then again with ECJ
  • Be tested with native-image
  • Include resources in native-image
  • Create CDI beans and interact with BeanContainer
  • Use substrate substitutions

(add more requirements here)

@starksm64
Copy link
Contributor

I can make a start on this. Should this be located in extensions/test?

@starksm64
Copy link
Contributor

core/test-extension was what was suggested on the call today.

@stuartwdouglas
Copy link
Member

Is this still relevant?

@dmlloyd
Copy link
Member Author

dmlloyd commented Nov 4, 2019

This is done.

@dmlloyd dmlloyd closed this as completed Nov 4, 2019
@gsmet gsmet added the triage/out-of-date This issue/PR is no longer valid or relevant label Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/out-of-date This issue/PR is no longer valid or relevant
Projects
None yet
Development

No branches or pull requests

4 participants