Issue #1645 Interface Support Mock Testing

.gitattributes

@@ -2,6 +2,7 @@
 
 *.bmp binary
 *.dll binary
+*.exe binary
 *.gif binary
 *.jpg binary
 *.png binary

CONTRIBUTION.md → .github/CONTRIBUTION.md

@@ -1,4 +1,4 @@
-#How to contribute?
+# How to contribute?
 There are many ways for you to contribute to OData Web API.  The easiest way is to participate in discussion of features and issues.  You can also contribute by sending pull requests of features or bug fixes to us.  Contribution to the documentations at our [GitHub Pages](http://odata.github.io/WebApi/) is also highly welcomed. 
 ##Discussion
 You can participate into discussions and ask questions about OData Web API at our [GitHub issues](https://github.com/OData/WebApi/issues). 
@@ -21,16 +21,16 @@ When reporting a bug at the issue tracker, please use the following template:
 *Optional, details of the root cause if known*  
 ```
 
-##Pull requests
+## Pull requests
 Pull request of features and bug fixes are both welcomed. Before you send a pull request to us, there are a few steps you need to make sure you've followed. 
-###Complete a Contribution License Agreement (CLA)
+### Complete a Contribution License Agreement (CLA)
 You will need to complete a Contributor License Agreement (CLA). Briefly, this agreement testifies that you are granting us permission to use the submitted change according to the terms of the project's license, and that the work being submitted is under appropriate copyright.
 
 Please submit a Contributor License Agreement (CLA) before submitting a pull request. Please fill and submit the [Contribution License Agreement Form | Microsoft](https://cla.microsoft.com/). Be sure to include your GitHub user name along with the agreement. Only after we have received the signed CLA, we'll review the pull request that you send. You only need to do this once for contributing to any Microsoft open source projects. 
 
-###Create a new issue on the issue tracker and link the pull request to it
+### Create a new issue on the issue tracker and link the pull request to it
 You should have an issue created on the [issue tracker](https://github.com/OData/WebApi/issues) before you work on the pull request. After the OData Web API team has reviewed this issue and change its label to "accepting pull request", you can issue a pull request to us in which the link to the related issue is included.
-###Requirement of pull requests
+### Requirement of pull requests
 Your pull request should:
 
  - Include a description of what your change intends to do
@@ -39,21 +39,13 @@ Your pull request should:
  - Include adequate function tests, corresponding E2E tests
  - Pass all tests without error
 
-###Run test
+### Run test
 Function test
 ```
-cd OData
-build
-```
-
-Corresponding E2E test
-```
-cd OData
-build E2EV3 (or E2EV4)
+build quick
 ```
 
 Or you can just run all test
 ```
-cd OData
-build FULL
+build
 ```

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,23 @@
+<!-- markdownlint-disable MD002 MD041 -->
+
+*Short summary (3-5 sentences) describing the issue.*
+
+### Assemblies affected
+
+*Which assemblies and versions are known to be affected e.g. OData WebApi lib 6.1.0
+
+### Reproduce steps
+
+*The simplest set of steps to reproduce the issue. If possible, reference a commit that demonstrates the issue.*
+
+### Expected result
+
+*What would happen if there wasn't a bug.*
+
+### Actual result
+
+*What is actually happening.*
+
+### Additional detail
+
+*Optional, details of the root cause if known. Delete this section if you have no additional details to add.*

.github/ISSUE_TRIAGE.md

@@ -0,0 +1,49 @@
+# Issue triage
+
+This document describes the triage process used for the [WebApi repository].
+
+## Prioritization
+
+We use customer feedback as our primary input for prioritizing issues.
+
+* P1: 5 or more asks, legal, or security issues
+* P2: 3-4 asks, regressions
+* P3: 2 asks
+* P4: 1 ask
+
+## What constitutes an "ask"
+
+We do our best to interpret customer feedback as asks. The easiest thing for us to interpret is opening an issue or an explicit comment on the issue stating that the fix would be helpful to a different party. We also make a best effort to interpret positive reactions as asks, although this interpretation is more subjective.
+
+Duplicate issues also constitute an "ask". You can help us identify duplicate issues by adding a comment to the issue that references the duplicate issue number.
+
+Finally, we also count asks from partner teams at Microsoft. We strongly encourage our colleagues to post the "ask" directly on GitHub; however that doesn't always happen.
+
+## Flagging regressions, legal, or security issues
+
+If an issue is a regression from a previous release, explicitly describe the issue as a regression so that we triage it appropriately. For legal or security issues, do not report the issue on GitHub but rather send us an e-mail at odatafeedback@microsoft.com.
+
+## Questions
+
+In general, we ask for questions to be posted on Stack Overflow rather than on GitHub. We tag issues that are actually questions with the question tag. In some cases we may answer the question directly; however we appreciate it the community handles the questions on a forum dedicated to answering questions.
+
+## Contributing fixes for P3/P4 issues
+
+While we appreciate all PRs, we especially count on the community to fix P3/P4 issues. The priority does not reflect the overall importance of an issue. It simply reflects the known asks we have for issues.
+
+Issue priority only affects the *order* in which we consider PRs. A PR for a P4 issue has as much likelihood of being accepted as a PR for a P1 issue.
+
+To contribute a fix for any issue, see our [contribution guidance][contributing].
+
+## Closing questions or issues with few asks
+
+Every so often we close issues that have remained at P3 or P4 for multiple months. If you still need a fix, it is perfectly acceptable to reopen issues. The best way to get a fix for an issue with few "asks" is to [send us a PR][contributing].
+
+We typically redirect questions to Stack Overflow, a forum better suited to getting answers for questions.
+
+## Feedback
+
+We are always open to feedback on how we should revise this process. Feel free to send your feedback to odatafeedback@microsoft.com.
+
+[WebApi repository]: https://www.github.com/odata/WebApi
+[contributing]: https://github.com/OData/WebApi/blob/master/.github/CONTRIBUTING.md

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,18 @@
+<!-- markdownlint-disable MD002 MD041 -->
+
+### Issues
+
+*This pull request fixes issue #xxx.*
+
+### Description
+
+*Briefly describe the changes of this pull request.*
+
+### Checklist (Uncheck if it is not completed)
+
+- [ ] *Test cases added*
+- [ ] *Build and test with one-click build and test script passed*
+
+### Additional work necessary
+
+*If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.*

.gitignore

@@ -35,3 +35,5 @@ project.lock.json
 *.ncrunchsolution
 *.*sdf
 *.ipch
+*.mdf
+*.ldf