<p>Hi Julian,<br>
Re. Testing<br>
I can recommend TestLink for managing the process. It integrates with some ticket systems and with Selenium too I believe. </p>
<p>Mark<br>
</p>
<div class="gmail_quote">On Sep 5, 2013 2:40 PM, "Julian Tenney" <<a href="mailto:Julian.Tenney@nottingham.ac.uk">Julian.Tenney@nottingham.ac.uk</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-GB" link="blue" vlink="purple"><div><p class="MsoNormal">Hi,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I think we’ve got the SVN migrated over to Git Hub with all the history, branches etc, which is great. We need to have some discussion about workflow, and I want to suggest gitflow as a good workflow to adopt. Information can be found here <a href="http://nvie.com/posts/a-successful-git-branching-model/" target="_blank">http://nvie.com/posts/a-successful-git-branching-model/</a> and elsewhere (here: <a href="https://www.atlassian.com/git/workflows" target="_blank">https://www.atlassian.com/git/workflows</a> for example).<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">I like it for several reasons:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>The ‘master’ branch is always production quality released code<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Small developments (trivial) can be undertaken directly in ‘develop’<u></u><u></u></p><p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Larger developments can be undertaken in braches taken from ‘develop’, and then merged back into develop once complete…<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>…testing of develop can then be undertaken before we make a new release number.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">See the information for more details. Does this seem sensible and agreeable to everyone?<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">
There are two other things I’d like us to work towards, again subject to some discussion between us:<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Using Tickets for Issues and New Features:<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Using some ticketing system to record bugs to be fixed, new features to be developed, because we keep losing these;<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Using those tickets as a way of grouping work into sprints towards a new release;<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Could be trac, could be github, open to suggestions;<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">A better means of testing the software rather than the hit and hope method we currently employ:<u></u><u></u></p><p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Open to suggestions here?<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Probably starts with a list of manual tests to work through?<u></u><u></u></p><p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>Possibly includes automation (Selenium?)<u></u><u></u></p>
<p><u></u><span>-<span style="font:7.0pt "Times New Roman""> </span></span><u></u><span dir="LTR"></span>UnitTesting probably a very long term goal, might not even be possible?<u></u><u></u></p><p class="MsoNormal">
<u></u> <u></u></p><p class="MsoNormal">So my vision would be that we log tickets, we use that list of tickets as a big to-do list; we create a smaller current to-do list from it for the next release; we do the development a la gitflow; changes get pushed to develop and tested; new version released. It sounds good in theory at any rate, it will require a bit more discipline amongst us, but I think the benefits are worth it. I’d very much appreciate your views…<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Thanks,<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Julian<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">
<u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p></div></div>
<br><p>This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.</p>
<p>This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation.</p>
<br><br>_______________________________________________<br>
Xerte-dev mailing list<br>
<a href="mailto:Xerte-dev@lists.nottingham.ac.uk">Xerte-dev@lists.nottingham.ac.uk</a><br>
<a href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev" target="_blank">http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev</a><br>
<br></blockquote></div>