-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #66 from mdsol/develop
Release of v5.0.0
- Loading branch information
Showing
33 changed files
with
686 additions
and
159 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Contributing | ||
|
||
## General Information | ||
* Clone this repo in your workspace. Checkout latest `develop` branch. | ||
* Make new changes or updates into `feature/bugfix` branch. | ||
* Make sure to add unit tests for it so that there is no breaking changes. | ||
* Commit and push your branch to compare and create PR against latest `develop` branch. | ||
|
||
## Running Tests | ||
To run tests, go the folder `mauth-client-dotnet\tests\Medidata.MAuth.Tests` | ||
Next, run the tests as: | ||
|
||
``` | ||
dotnet test --filter "Category!=ProtocolTestSuite" | ||
``` | ||
|
||
## Running mauth-protocol-test-suite | ||
To run the mauth-protocol-test-suite clone the latest suite onto your machine and place it in the same parent directory as this repo (or supply the ENV var | ||
`TEST_SUITE_PATH` with the path to the test suite relative to this repo). | ||
Then navigate to :`mauth-client-dotnet\tests\Medidata.MAuth.Tests` | ||
And, run the tests as: | ||
|
||
``` | ||
dotnet test --filter "Category=ProtocolTestSuite" | ||
``` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.