Skip to content

Latest commit

 

History

History
73 lines (50 loc) · 3.9 KB

README.md

File metadata and controls

73 lines (50 loc) · 3.9 KB
Raw

LodeRunner.UI

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.

Development Experience

Initial Setup

  1. Setup LodeRunner and LodeRunner.API pods (Instructions at Running the System via Codespaces)
  2. Change into the LodeRunner.UI directory cd src/LodeRunner.UI
  3. Set the endpoint LodeRunner.UI makes API calls to
    • In Codespaces, navigate to the PORTS terminal
    • Identify port LodeRunner API (32088) and hover over the Local 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
  4. Install node dependencies in npm install
  5. Start the client npm start

Re-run

  1. Verify in loderunner directory
  2. Set environmental variables for K8S generic secret via source ~/.lr.env
  3. Start the k3d cluster make create
  4. Deploy LodeRunner, LodeRunner.API, LodeRunner.UI make lr-local
  5. Set LodeRunner.API port visibility to public
    • In Codespaces, navigate to the PORTS terminal
    • Identify port LodeRunner API (32088) and right-click on the Visibility
    • Hover over Port Visibility and select Public
  6. Change into the LodeRunner.UI directory cd src/LodeRunner.UI
  7. Start the client npm start

Testing the Client Application

Launch the test runner, jest, in the interactive watch mode: npm test

Linters

  • npm run lint: Runs ESLint and automatically fixes recommended changes
  • npm run lint-audit: Runs ESLint and lists recommended changes
  • npm run format: Runs Prettier and automatically fixes recommended changes

Fix dependency vulnerabilities

  1. Verify dependencies that require fixing
    • npm audit --production
    • Explanation: facebook/create-react-app#11174
    • NOTE: Please do not move react-scripts to devDependencies as suggested in the above article. This will break the docker image build.
  2. Automatically fix dependencies: npm audit fix

Production Build

  • npm run build: Builds app for production and saves in the build folder
  • npm run build-prod: Builds app for production and saves in the build folder without ESLint errors

Contributing

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 https://cla.opensource.microsoft.com

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 opencode@microsoft.com with any additional questions or comments.

Trademarks

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.