[almighty] ALR’s talk on Test Driven Development and GIT stuff

[Sudipta Sen]

In order to do development :

* Fork it
* Identify the issue
* Post the issue and discuss
* Branch out of master with a sensible name ( Use the issue ID in the name
for reference )
* Run test on your  new branch
* Write a test on your hypothesis
    * Name the test with a sensible one.
    * Create a test that fails showing the issue
    * Give a comment with the issue ID.
    * Sensible test error message should contain the issue ID for reference.
    * Follow Idempotent in test.
        * Write a test that can be run again and again.
        * That test should not have any side effect.
* git status to see all the changes that you have made so far.
* git diff to review your code changes so far.
* git commit -a the changes with a sensible commit message, maybe with the
issue ID for reference.
* git checkout master
* git pull upstream master
* git checkout <your branch>
* git rebase master
    * Fix all the conflicts
* git push <your remote> <your branch>
* Create a pull request to the master.
* After the pull request is accepted it’ll be in master of upstream.
* Delete your branch locally and remote as well.



-- 

*Sudipta Sen*Software Engineer

M: (+91) 906 625 8469
E: sudsen at redhat.com <brittney at gopassport.com>
E: sanborn.sen at gmail.com <brittney at gopassport.com>
<http://www.gopassport.com/>

[image: Facebook] <https://www.facebook.com/ssudipta.ssen> [image: Linkedin]
<https://in.linkedin.com/in/sudipta-sen-16247455> [image: Twitter]
<https://twitter.com/SudiptaSen7>

[image: http://redhat.com/] <http://redhat.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160916/2af50614/attachment.htm>