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

RevEng: add tests #1669

Closed
lajones opened this issue Feb 20, 2015 · 8 comments
Closed

RevEng: add tests #1669

lajones opened this issue Feb 20, 2015 · 8 comments
Assignees

Comments

@lajones
Copy link
Contributor

lajones commented Feb 20, 2015

Part of #830. Need to come up with a testing strategy and implement more tests for Reverse Engineering.

@lajones
Copy link
Contributor Author

lajones commented Jun 9, 2015

Added end-to-end test on release branch (dnx451 only) with commit 1d973a1.

@bricelam
Copy link
Contributor

(Copying my comment from an earlier PR:)

I think for functional tests, it would good to hit a database and/or compile code. The two big functional scenarios I see are:

  • Create various database objects, verify SqlServerMetadataModelProvider outputs a correct model
  • Create various models, generate code, verify code, compile code, verify model

@lajones
Copy link
Contributor Author

lajones commented Jun 11, 2015

Merged the end-to-end test for dnx451 into dev branch with commit 776124e.

@lajones
Copy link
Contributor Author

lajones commented Jun 23, 2015

E2E test is updated to work on dnxcore50 as well. See #2452.

@lajones
Copy link
Contributor Author

lajones commented Jul 9, 2015

Added compilation test with #2575

@rowanmiller
Copy link
Contributor

@lajones what is still outstanding here?

@rowanmiller rowanmiller removed this from the 7.0.0 milestone Sep 17, 2015
@lajones
Copy link
Contributor Author

lajones commented Sep 17, 2015

The standard RevEng capabilities are covered through the end-to-end tests, but would like to add more unit tests.

@rowanmiller
Copy link
Contributor

Closing, feel free to incrementally add coverage as you work on things.

@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
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

4 participants