trustchain-oc1-orchestral/IdHub_E2E_testing
Archived
10
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

modify pipeline integration

Browse source
This commit is contained in:
mildred 2024-03-07 11:48:17 +01:00
parent 76e20770d9
commit 836c66ee9a
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
README.md
View file

@ -6,6 +6,7 @@
- [Installation](#installation) - [Installation](#installation)
- [Usage](#usage) - [Usage](#usage)
- [Test Structure](#test-structure) - [Test Structure](#test-structure)
- [Pipeline Integration](#Pipeline-integration)
- [License](#license) - [License](#license)
## Introduction ## Introduction
@ -129,7 +130,9 @@ The tests directory is where all test files are stored. These test files contai
describe describe
## GitHub Actions Workflow Configuration for Running Playwright Tests ## Pipeline integration
### GitHub Actions Workflow Configuration for Running Playwright Tests
Following we outline the configuration of a GitHub Actions workflow designed to running tests on GitHub using GitHub actions It breaks down the key components of the workflow to ensure clarity and understanding. Following we outline the configuration of a GitHub Actions workflow designed to running tests on GitHub using GitHub actions It breaks down the key components of the workflow to ensure clarity and understanding.
```yaml ```yaml
@ -162,25 +165,25 @@ jobs:
retention-days: 30 retention-days: 30
``` ```
### Workflow Name #### Workflow Name
- **Workflow Name**: The name of this workflow is "Playwright Tests". This identifier is used within GitHub Actions to reference this workflow. - **Workflow Name**: The name of this workflow is "Playwright Tests". This identifier is used within GitHub Actions to reference this workflow.
### Trigger Events #### Trigger Events
- **Push to Main or Master Branches**: The workflow is triggered on any push event to the `main` or `master` branches. - **Push to Main or Master Branches**: The workflow is triggered on any push event to the `main` or `master` branches.
- **Pull Requests to Main or Master Branches**: Similarly, the workflow is also triggered upon any pull request that targets the `main` or `master` branches. - **Pull Requests to Main or Master Branches**: Similarly, the workflow is also triggered upon any pull request that targets the `main` or `master` branches.
### Jobs #### Jobs
- **Jobs**: The workflow defines a job named `test`. This job is executed when the workflow is triggered. - **Jobs**: The workflow defines a job named `test`. This job is executed when the workflow is triggered.
### Job Configuration #### Job Configuration
- **Timeout**: A timeout of 60 minutes is set for this job. If the job exceeds this time, it will be automatically canceled. - **Timeout**: A timeout of 60 minutes is set for this job. If the job exceeds this time, it will be automatically canceled.
- **Environment**: The job is configured to run on the latest version of Ubuntu provided by GitHub Actions. - **Environment**: The job is configured to run on the latest version of Ubuntu provided by GitHub Actions.
### Steps #### Steps
1. **Checkout Repository**: The first step checks out the repository, allowing the workflow to access it. 1. **Checkout Repository**: The first step checks out the repository, allowing the workflow to access it.
- `uses: actions/checkout@v3` - `uses: actions/checkout@v3`