-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(Cypress): Add cypress e2e project #241
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: hoangnt2 <[email protected]>
We have implemented e2e testing for components and releases. Please take a look at it and if you have any questions, please let me know. |
@heliocastro @ag4ums @amritkv @arunazhakesan Please feel free to comment for this PR! |
Hey @KoukiHama & @hoangnt2 ! It looks awesome to me, as of now ! Need to dig deeper to understand it's usages in complex scenarios like tables. |
…er Token to Basic Auth
79eb089
to
e5937e1
Compare
…tabs for the release after an update
Pre-condition:
New front-end commit id: f8d8183
How To Test?
1. Requirement software
$ sudo apt-get update $ curl -sL https://deb.nodesource.com/setup_20.x | sudo -E bash - $ sudo apt install nodejs -y // Check nodejs version $ nodejs -v
Note: Recommended environment is Ubuntu 22.04 LTS, Nodejs v20.5.0, NPM 10.2.5
2. Setup project
$ git clone https://github.com/eclipse-sw360/sw360-frontend.git $ cd sw360-frontend
Reference: https://docs.cypress.io/guides/getting-started/installing-cypress#System-requirements
3. Run Testing
3.1. Setup testing
Change cypress configuration
Change these configs, keep others:
3.2. Prerequisite:
3.3. Run with Cypress UI
$ npm test
3.4. Run in headless mode
Run all tests:
Run a specify test:
Limitation