October 14, 2019
GitHub is a hosting platform and version control for software development. It is a place where developers network with people and store their projects.
GitHub’s Fundamental Elements
The Repository can be used to store the project. It can store all types of file such as images, data, HTML, CSS, etc. in a folder. It should include a license and a read me file including information about the project.
The Branch is used by developers to work with different versions at the same time. By default, there is a master branch known as the production branch in the repository. Any other branch created for bug fixing and feature work is a copy of the master branch. Once the changes done in the code are ready, they can be merged into the master branch.
Commits are the changes done in the code. These commits include the description and reason for the change.
Pull Requests are the heart of GitHub collaboration. When a request is polled you can propose that your changes are merged in the master branch. They show the differences, addition, subtraction, and changes through colors. One can start a discussion in a pull request as soon as you commit.
Git is an open-source version and a command-line tool started by Linux, which is used for storing the changes of the code in a common repository.
Developers create software or an application and they constantly make changes to the code before the release of the beta version. Git stores these changes in a central repository. Due to this, the developer can easily update the code changes which are visible to every developer of the team.
Eliminate bugs and ship with more confidence by adding GitHub to your Automation Workflow
10 steps to follow while integrating Git with TestingWhiz
1. Click on Setting > Configuration > Version Control > Git
2. Click ‘Add’ to add Git Version Control details
3. Click ‘OK’ and ‘Test Connection’ to verify values provided to the repository
4. Select Version Control type from Git or SVN and it's alias accordingly and output would be as per below image
5. Select a file from the provided list and click save.
a) If SVN selected then provides a path for output file
b) If Git selected then the file will be available at local repository and the selected file will open in TW tool.
6. After checkout, all options will get enable in project right click > Team > Version control options
7. Project right click > Team > Select any option of your choice and each option will work as per the below detail.
a) Select Commit from Team
b) Select Version control from dropdown and alias from alias dropdown after both combo selection repository URL will get display corresponding to alias
c) Provide commit message and click OK and it will get commit to the repository
a) Shows logs of file (i.e. logs of file open in TW)
b) Selection of any log will open revision file in TW
c) It will not be saved at any location in the system and If you want to make changes to that file, then the file needs to be saved by clicking File > Save As before committing file to the repository.
d) Only checkout option will be enabled for the file open using Show History.
a) Reverts to last committed revision of file (i.e. file open in TW).
b) Only works for File selected from checkout and not with file selected from show history. So, it will be disabled if the show history file is selected.
Note: In the previous release 6.3, TestingWhiz has added Support for Git/BitBucket integration for Version Control Management.
Git helps you get a central platform where the developers can review each other’s code and they can also make necessary changes if it is required.
Integrating Git with TestingWhiz helps you proactively control access to your code. To know more about Git and various possibilities for working with repositories and code, email us at firstname.lastname@example.org or call us on +1-855-699-6600