зеркало из
1
0
Форкнуть 0

Adding documentation on testing

This commit is contained in:
Darren Hoehna 2019-11-01 20:33:37 -07:00
Родитель aa6a7e951c
Коммит 8af3e1ddaa
2 изменённых файлов: 35 добавлений и 0 удалений

Просмотреть файл

@ -43,6 +43,11 @@ Here is how you can contribute to the Package Support Framework:
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
### Testing your changes.
Before making a pull request please run the regression tests to make sure your changes did not break existing behavior.
Please head to the tests solution and follow the instructions inside readme.md.
## Script support
Scripts allow IT Pros to customize the app for the user environment dynamically. The scripts typically change registry keys or perform file modifications based on the machine or server configuration.

30
tests/README.md Normal file
Просмотреть файл

@ -0,0 +1,30 @@
#Testing
Package Support Framework has several regression tests that are required to pass before your code will be pulled into the develop branch.
Below will be two sets of instructions. One set will tell you how to run all the tests. The second set will tell you how to debug tests.
##How Package Support Framework runs tests
Because Package Support Framework needs to hook into an application all tests are packaged into an application, installed on your computer, then ran.
At the end of the RunTests.ps1 script all the applications are removed.
##Running all tests.
Please follow the instructions to run all the tests and see if they all pass.
1. Open a admin Visual Studio developer command prompt.
2. Navigate to the root of the repository (MSIX-PackageSupportFramework)
3. Run "buildall.cmd"
1. If you have build errors please fix them before continuing.
4. Open an amin powershell prompt.
5. Navigate to the tests directory of the repository.
6. run ".\runtests.ps1"
Wait for the tests to run and finish. When the script is finished it will tell you how many tests failed. If no tests failed you can make the pull request.
##Debugging tests
Sometimes our changes will make a test fail. If that is the case you might need to debug a test to figure out why it failed so you can fix your code.
Please follow the below steps to debug tests.
1. Run the tests in the "Running all tests" section to see