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

[Andrew Lee Rubinger]

Great stuff!

As a bonus I might recommend taking these practices that Sudipta has
compiled and throwing them into the Almighty devdocs. :)

S,
ALR

On Mon, Sep 19, 2016 at 8:19 AM, Sudipta Sen <sudsen at redhat.com> wrote:

> Sure. It'll be a nice guide line.
>
> On Mon, Sep 19, 2016 at 4:05 PM, Konrad Kleine <kkleine at redhat.com> wrote:
>
>> Sorry, wrong PR. This one is the correct one: https://github.com/almigh
>> ty/almighty-core/pull/249 This one applies some of the proposed
>> guidelines: https://github.com/almighty/almighty-core/pull/240
>>
>> On Mon, Sep 19, 2016 at 12:33 PM, Konrad Kleine <kkleine at redhat.com>
>> wrote:
>>
>>> Hi Sudipta,
>>>
>>> I've create a commit a few days ago and lately a PR. Maybe we can
>>> integrate your or ALR's ideas into that document.
>>>
>>> https://github.com/almighty/almighty-core/pull/240
>>>
>>> So far I've just added notes on a few techniques in Go that are special.
>>>
>>> Regards,
>>> Konrad
>>>
>>>
>>>
>>> On Fri, Sep 16, 2016 at 12:00 PM, Sudipta Sen <sudsen at redhat.com> wrote:
>>>
>>>> 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/>
>>>>
>>>> _______________________________________________
>>>> almighty-public mailing list
>>>> almighty-public at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/almighty-public
>>>>
>>>>
>>>
>>
>
>
> --
> --
>
> *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/>
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
>


-- 
Red Hat Developer Programs Architecture
@ALRubinger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160919/05e44b4d/attachment.htm>