Skip to content
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.

Sign up for GitHub

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

Jump to bottom

added readme document #159

Merged
merged 2 commits into from
Sep 20, 2024
Merged

added readme document #159

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98a95e7
added readme file
anup-nehe Sep 20, 2024
5c70a17
Merge remote-tracking branch 'upstream/release-0.10.x' into release-0…
anup-nehe Sep 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions ui-test/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Inji verify Automation - web Automation Framework using selenium with cucumber

## Overview

uitest-injiverify is a automation framework designed for inji verify web app. It automates both positive and negative scenarios to ensure comprehensive testing of web applications.

## Pre-requisites

Ensure the following software is installed on the machine from where the automation tests will be executed:
- Java 21
- Maven 3.6.0 or higher

## Build
1. Clone the repository by git clone https://github.com/mosip/inji-verify.git
2. Change directory by using command 'cd ../uitest-injiverify' & Build the JAR file: `mvn clean package -DskipTests=true`
3. The JAR file will be generated in the `target` directory.
4. For running tests on Device Farm, use the JAR file with dependencies (`zip-with-dependencies`).

## Configurations

1. Update `featurefile>>UploadQRCodepage.feature` to modify data in examples section.


## Reports

Test reports will be available in the `test-output>>ExtentReports>>SparkReports` directory after test execution.
Loading