Page Comparison

eGov Main : https://github.com/egovernments

...

Repo Link : https://github.com/egovernments/test-automation/

1. Automation

...

1. Team Pull Requests Branch for Karate Framework : karate-master

 Total we have as of now 5 branches:

...

Karate-master

https://github.com/egovernments/test-automation/tree/karate-master

2. Automation Master Branch for Client’s handover Karate Framework : master (Default)

https://github.com/egovernments/test-automation/tree/master

3. Automation Branch Previous Code : cypress-master-backup. (Back up of Initial Cypress Code)

https://github.com/egovernments/test-automation/tree/cypress-master-backup

Sub-Branches for automation Engineers - Local working tree branches:

1. Automation-phase-0

2. Automation-phase-1-kh (for krishnendu)

3. Automation-phase-1-sm (for sarita)

4. Automation-phase-1-yb (for yatheendra)

5. Automation-phase-1-ss (for Shareef)

 Pull Request Process :

Source branch : any Engineer has to choose their corresponding code tree branch of the among above branches and raise Pull Request for review.

Destination branch : karate-master

...

1. Jira story should be created in backlog.

2. Above jira story should be pulled in into the current sprint.

3. Same story can be pulled into in progress once we start working on that till then it will be there in TO DO.

4. Once test cases created, then raise PR (Pull Request) against karate-master and mark the Jira status as Ready for Review and assign it to the Reviewer.

5. Once PR Review is over post fixing the comments then merge with karate-master and mark the jira story state as Done.

...