LodeRunner.UI is intended to facility testing in controlled environments by providing the frontend to interact with LodeRunner.API. LodeRunner.API creates/updates/deletes load test configs in CosmosDB, that would be executed by LodeRunner without restarting the load client.
- Setup LodeRunner and LodeRunner.API pods (Instructions at Running the System via Codespaces)
- Change into the LodeRunner.UI directory
cd src/LodeRunner.UI
- Set the endpoint LodeRunner.UI makes API calls to
- In Codespaces, navigate to the
PORTS
terminal - Identify port
LodeRunner API (32088)
and hover over theLocal Address
- Click on the clipboard icon to copy the local address
- Open
.env.development
- Set
REACT_APP_SERVER
to copied LodeRunner.API URL - Prevent accidental commits with
git update-index --assume-unchanged .env.development
- In Codespaces, navigate to the
- Install node dependencies in
npm install
- Start the client
npm start
- Verify in loderunner directory
- Set environmental variables for K8S generic secret via
source ~/.lr.env
- Start the k3d cluster
make create
- Deploy LodeRunner, LodeRunner.API, LodeRunner.UI
make lr-local
- Set LodeRunner.API port visibility to public
- In Codespaces, navigate to the
PORTS
terminal - Identify port
LodeRunner API (32088)
and right-click on theVisibility
- Hover over
Port Visibility
and selectPublic
- In Codespaces, navigate to the
- Change into the LodeRunner.UI directory
cd src/LodeRunner.UI
- Start the client
npm start
Launch the test runner, jest, in the interactive watch mode: npm test
npm run lint
: Runs ESLint and automatically fixes recommended changesnpm run lint-audit
: Runs ESLint and lists recommended changesnpm run format
: Runs Prettier and automatically fixes recommended changes
- Verify dependencies that require fixing
npm audit --production
- Explanation here
- NOTE: Please do not move react-scripts to devDependencies as suggested in the above article. This will break the docker image build.
- Automatically fix dependencies:
npm audit fix
npm run build
: Builds app for production and saves in thebuild
foldernpm run build-prod
: Builds app for production and saves in thebuild
folder without ESLint errors
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit Microsoft Contributor License Agreement
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services.
Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines.
Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship.
Any use of third-party trademarks or logos are subject to those third-party's policies.