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

Add more test coverage for tooling/RevEng #9111

Closed
ajcvickers opened this issue Jul 7, 2017 · 3 comments
Closed

Add more test coverage for tooling/RevEng #9111

ajcvickers opened this issue Jul 7, 2017 · 3 comments
Assignees
Labels
area-test closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@ajcvickers
Copy link
Member

ajcvickers commented Jul 7, 2017

No description provided.

@ajcvickers ajcvickers added this to the 2.1.0 milestone Jul 7, 2017
@smitpatel smitpatel self-assigned this Jul 7, 2017
@smitpatel
Copy link
Member

@bricelam - Heads up. I am going to start working on modifying reveng tests as we discussed earlier.

@smitpatel
Copy link
Member

Summary of a recent discussion about testing of tools interface
There are 3 splits of tests needed.

  1. PMC/dotnet ef calling into mock ef.exe with correct parameters.
  2. ef.exe calling into mock executor.
  3. Executor calling into right entry points into (mock) design assembly.

Above would verify, from command to design assembly entry point pipeline is working correctly.
Inside design assembly there are tests based on the scenarios.

@bricelam
Copy link
Contributor

bricelam commented Dec 5, 2017

We also intend to add some IModel -> C# tests. (started in bricelam:gen)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Development

No branches or pull requests

3 participants