This repository has been archived by the owner on Oct 5, 2022. It is now read-only.
🧪 Create integration tests for help view #111
Labels
status/blocked-help-needed
This issue is blocked and needs support
type/feature-request
New feature or request
🧪 This is the view that should be tested
💻 How to run this project locally
Fork this repository by clicking on fork button on the top right. This will create a copy of this repository on your account.
Clone your fork.
Get the URL of your fork by clicking on
code
button on GitHub.Clone it to your local with command
git clone <URL you copied>
git clone <https://github.com/><your-username>/dashboard.git
.Install dependencies using command
npm i
.Run in the debug mode
npm run start_dev-server
testServer will be running on
http://localhost:5000
by defaultnpm run start-dashboard
Dashboard will be served on
http://localhost:3000
by default🏃♀️ How to get there.
Click on the option
Help
from the sidebar on the leftThe component of interest are NotFound
🧪 How to run integration tests
Run
npm run cy:dev
from your console. This will open cypress and you can run the test suites you want to run by clicking on it.When you're done working, make sure that
npm run cy:run
passes without any errors.📝 Where to make changes?
In
cypress/integration/views
directory and in the components you want to test.Check this pull request
Pay attention to the changes in files
cypress/integration/views/logsView.ts
andsrc/components/LogStream/BarChartBase.tsx
. You'll have to make similar changes.📖 How to learn about writing integration tests?
We use a framework called cypress for integration tests. Their documentation is quite helpful.
Go through their best practices, interacting with elements, structuring tests and you'll get a great understanding of how to write good integration tests
🖐️ I want to work on this.
If you're interested in working on this issue, please write a comment down below. 💬
If you need any help or have questions, you can ask questions here or ask in our slack group
The text was updated successfully, but these errors were encountered: