Git Basics
This command creates a new branch and switches you to it in one step.
git checkout -b <branch-name>
Tests that verify a change did not break existing behavior belong to this type of suite.
Test cases grouped for execution are organized under this folder in Katalon.
Test Suites
This Git action creates a separate line of development so you can work on a feature without changing main.
A branch
What does CI stand for?
Continuous Integration
This Git area holds changes after git add but before git commit
The staging area
In UI automation, this "repository" stores locators and page elements for reuse in Katalon.
Object Repository
Environment-specific global values like default and test are stored here.
This command creates a new branch and switches to it immediately.
git checkout -b <branch-name>
What does CD stand for?
Continuous Delivery or Continuous Deployment
This command shows the current branch and modified or untracked files.
git status
Instead of hardcoding values into every test, teams often store them in this Katalon folder.
Data Files
Shared lifecycle hooks like cleanup and failure handling are implemented in this Katalon area.
Test Listeners
When Git cannot automatically combine changes from two branches because the same area of code was edited differently, it reports this problem.
A merge conflict
What is the purpose of CI?
Automate building and testing code changes
When two branches edit the same lines differently, Git reports this type of conflict.
Running the same tests against different browsers, profiles, or environments is called this.
parameterized execution
In the project READMEs, browser desired capabilities and execution behavior are said to live under this path.
settings/internal
After fixing conflicting code by hand, this Git action marks the conflict as resolved so the merge can continue
git add <file>
What is a pipeline?
An automated workflow of build/test/deploy steps
This command downloads remote changes and combines them into your current branch.
git pull
A screenshot taken automatically after a failure is mainly useful for this post-run activity.
debugging test failures
The project READMEs mention this Java version as matching build.gradle.
Java 17
In a long-lived feature branch, regularly bringing in the latest changes from main helps reduce the size and complexity of these later integration problems.
Merge Conflicts
Name a CI/CD tool used at our company
Azure DevOps or Github Actions