From the course: Robot Framework Test Automation: Jenkins CI and Git Version Control

Unlock this course with a free trial

Join today to access over 22,600 courses taught by industry experts.

Save script changes to a remote repo

Save script changes to a remote repo

- [Instructor] So now let's take a look at how we're going to persist any changes we make locally here up into the GitHub cloud. If I double click my Amazon.robot file here and scroll down to one of the test cases, you'll notice that the name of my script file here is black. The minute that I make any change to the file, I've just added two spaces there, now you see that that file name turned to blue and down here in our Version Control pane we can see that we have a new node here called default. And when I expand that we can see that Git via the Python UI is tracking changes to these files relative to the version that exists in our local version of Git. So when I add a new tag here I have changed my local file, but the file up here on the server has not yet changed. You can see that it still has only that one tag on it. So now the typical Git workflow would be for me to test my change, run it and make sure it works. And you can see down here if I click on this file now there's a…

Contents