Skip to content

Commit 0ec5f1a

Browse files
Update README.md
1 parent 1918279 commit 0ec5f1a

1 file changed

Lines changed: 50 additions & 2 deletions

File tree

README.md

Lines changed: 50 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,50 @@
1-
# SetviTechnicalTask
2-
https://pavlovic-bojan.github.io/SetviTechnicalTask/
1+
# Setvi Technical Task
2+
3+
This repository is the result of my independent project for SETVI.
4+
5+
## What can you find here
6+
* Quick summary about this repo: I spent 2 days on the realization and setting up this project. The JavaScript programming language was used to write the code. The URL for the endpoint I got for SETVI, and I had no intention of harming the company itself, but only to increase and improve my skills.
7+
* Folder structure: inside the Cypress folder, there is an e2e folder containing a test file. The main class is located in the modules folder, which is also inside the cypress folder, and this class contains all the methods..
8+
* Side information: To use the application in a special environment, the author accepts no responsibility if you cause damage to third parties
9+
* Detailed bug report [5 positive, 5 negative](https://github.com/pavlovic-bojan/SetviTechnicalTask/blob/main/BUG_REPORT/BUG_REPORT.md)
10+
11+
## Execution of tests in CI/CD using GitHub Actions
12+
Go to [Actions](https://github.com/pavlovic-bojan/SetviTechnicalTask/actions), then choose on the left side [Setvi Technical Task](https://github.com/pavlovic-bojan/SetviTechnicalTask/actions/workflows/main.yml), then on the right side click on Run workflow in the text box, insert branches if not want to run from the main branch, and then click on the green button Run workflow.
13+
***
14+
[The results of the last test execution are visible at this link](https://pavlovic-bojan.github.io/SetviTechnicalTask/)
15+
> In the meantime, if the owners changed something on the endpoint and some tests failed, maybe all the tests failed due to changes in the endpoint itself. I don't have any influence, nor is the company obliged to let me know about changes, because this project is only a demo project.
16+
17+
## How To Clone and Set Up a Project
18+
19+
### Install the dependencies
20+
```bash
21+
npm ci
22+
```
23+
### Run Cypress test locally in the terminal
24+
```bash
25+
npm run cy:run
26+
```
27+
### Clear Allure Report locally for the previous run
28+
```bash
29+
npm run allure:clear
30+
```
31+
### Generate Allure Report locally for the last run
32+
```bash
33+
npm run allure:report
34+
```
35+
36+
## A list of technologies used within the project
37+
***
38+
A list of technologies used within the project:
39+
* [macOS Sonoma](https://support.apple.com/en-us/HT214032): macOS Sonoma Version 14.1.2 (23B92)
40+
* [Intellij idea](https://www.jetbrains.com/idea/): Version 2022.3.3
41+
* [Cypress](https://www.cypress.io/) Cypress 14.4.0
42+
* [@shelex/cypress-allure-plugin](https://www.npmjs.com/package/@shelex/cypress-allure-plugin) @shelex/cypress-allure-plugin 2.41.2
43+
44+
Feel free to copy the project from this repository into your IDE, run the test, and make sure all the scenarios are automated.
45+
46+
## Collaboration
47+
***
48+
This is my project, which I upgrade with new things and test scenarios from time to time, and I do not accept any collaboration
49+
> Please do not change the code.
50+
> I am available for any questions.

0 commit comments

Comments
 (0)