Closed taranjitsinghboparai closed 7 years ago
Testing is associated with specific production code and each test could be a separate issue.
Best Regards, Hao C. Lac, Ph.D. (Computational Science)
On Sat, Feb 25, 2017 at 2:35 AM, taranjitsinghboparai < notifications@github.com> wrote:
Closed #10 https://github.com/taranjitsinghboparai/COMP313-002-Team4/issues/10.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/taranjitsinghboparai/COMP313-002-Team4/issues/10#event-977014087, or mute the thread https://github.com/notifications/unsubscribe-auth/ADr-JodiLWr2bwdUEuE6klUs2VFsvr80ks5rf9nLgaJpZM4L2mgD .
Instead of assigning a dedicated person to perform testing, you'll notice that each source file that you work on is based off of an issue (e.g. task equivalent to an issue). So when you commit your source, make sure you include in the commit message the integer identifier for the given issue. This will generate a link in your issue leading back to the code. So when you perform testing, you can close it with a closing keyword in your commit message.