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

Update README.md with videos which can help people #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md with videos which can help people #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 7 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,12 @@ Following are some features of Syncer on high-level:
- Support for providing particular Test Suites in which test-cases needs to be updated or in case of same test-case present in multiple test suites
- List down the test-cases which are not part of Azure DevOps

## Videos which can assist you in using the utility

[![How to use the utility locally](http://i3.ytimg.com/vi/Zjxrv3_J2BM/hqdefault.jpg)](https://www.youtube.com/watch?v=Zjxrv3_J2BM)

[![Integrate utility with pipeline](http://i3.ytimg.com/vi/U8cZKv5f7hE/hqdefault.jpg)](https://www.youtube.com/watch?v=U8cZKv5f7hE&feature=youtu.be)

## Usage
Generally, there are 2 types of Test Execution.
1. Automated Test Execution - Testers automate their test-cases using any automation framework and execute them which will generate a file with Test results.
Expand Down Expand Up @@ -203,4 +209,4 @@ USAGE: syncer --version
-c (Default: false) true/false. Use this argument to specify
that specified Test-suite Ids should only be considered
for duplicate Test-cases
```
```