-
Notifications
You must be signed in to change notification settings - Fork 84
Setup Development Environment
Chandni Patel edited this page May 28, 2024
·
7 revisions
- Node 20.x LTS
- Git
- Owner-role access to this repository
- Fork this GitHub Action repository into your own namespace
- Clone your own repo by
git clone https://github.com/<your_namespace>/functions-action.git - Change your directory
cd functions-action - Install node dependencies
npm install
WARNING: In the current state of the repo, the action is not able to run locally.
Head to ./src and focus on changing the *.ts file. After that, ensure new unit test cases are added in ./tests folder by changing those *.spec.ts files.
- To run all tests across all different cases:
npm run test - To run unit tests on a specific file:
npm run test-file <file_path> (e.g. npm run test-file .\tests\utils\client.spec.ts)
- Please review or add the sample apps in
.\tests\e2e\folder. - Please review or modify workflow files in
.\.github\workflows\run-e2e-tests-*.yml.- Change AZURE_FUNCTIONAPP_NAME to the one you created.
- Change ${{ secrets.GAE_FA_DOTNET3_LCON }} to the one secret created in your GitHub repository.
- Create a secret GAE_FA_DOTNET3_LCON in your GitHub repository. Copy the publish profile xml context into its value.
- Every time when you push to
devbranch ormasterbranch, the E2E tests now should be triggered.
WARNING: When creating the pull request to Azure/functions-action, remember to remove the E2E workflow .yml files