<div dir="ltr">Hi,<div>I will try to list the few ways I use to test. Also whichever way you use, I recommend mentioning it briefly in your commit messages.</div><div><br></div><div>Check the log files after changes. Log files contain tracebacks....</div><div><div dir="auto">- for activities see `~/.<span class="gmail-il">sugar</span>/default/logs/activity_bundle_id.log`</div><div dir="auto">- for <span class="gmail-il">sugar</span> refer to the logs `~/.<span class="gmail-il">sugar</span>/default/logs/shell.log`</div></div><div dir="auto"><br></div><div dir="auto">- you may make changes to a source repository clone in /usr/src/sugar of Sugar Live Build and then run autogen, "make", and "make install". However, there are other things you need to take care of. Refer to: <a href="https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md</a><br><br></div><div>Making changes to the Sugar Activities:</div><div>Before you make any changes to the source code it is imperative to know how the activity works without these changes.</div><div>While testing lookout for:</div><div>- Your code does not make an unintentional change. By that I mean in the process of solving one issue, you do not create another.</div><div>- Design tests and iterate until the tests have sufficient coverage for the code changes.</div><div><br></div><div>As Srevin and James mentioned, there can be more to testing depending on what part of code you are working on. </div><div>I hope our emails help.</div><div><br></div><div>Regards,</div><div>Jui</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 13, 2021 at 2:14 AM James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I agree, there is no simple explanation for how to test code, as it<br> depends exactly on where the change is made.<br> <br> However, I'm surprised if one would ever reach the point of having to<br> test a change without knowing how to run the program that you are<br> about to change. That would be very much going forward blindly.<br> <br> On Tue, Jan 12, 2021 at 08:19:51PM +0300, Srevin Saju wrote:<br> > It would be quite complicated to explain what to check. We would be able to<br> > explain better if you could send a draft Pull Request and ping me there.<br> > <br> > Some basic ways to test, common to all activities / sugar / any FOSS<br> > software would be to:<br> > <br> > 1. Clone the source, checkout master<br> > 2. Login to Sugar<br> > 3. Run the software / activity : (in sugar, it would be to run `python<br> > setup.py install` or `python setup.py dev`, click on the activity's<br> > icon on the Sugar Home view<br> > 4. Make your changes, GOTO STEP 2 and repeat those with your new changes.<br> > 5. Finally, push your changes when you are satisfied.<br> > 6. Have fun.<br> > <br> > On 1/12/21 8:08 PM, Kunal Tulsidasani wrote:<br> > > Thankyou for your reply!<br> > > <br> > > I have read this file and this shows on what bases to check!<br> > > <br> > > I want to know how to check? Like what should I do?<br> > > <br> > > Regards<br> > > Kunal<br> > > <br> > > On Tue, 12 Jan 2021, 22:26 Srevin Saju, <<a href="mailto:srevinsaju@sugarlabs.org" target="_blank">srevinsaju@sugarlabs.org</a><br> > > <mailto:<a href="mailto:srevinsaju@sugarlabs.org" target="_blank">srevinsaju@sugarlabs.org</a>>> wrote:<br> > > <br> > > You might be interested in<br> > > <a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone</a><br> > > <<a href="https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone" rel="noreferrer" target="_blank">https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone</a>><br> > > <br> > > . You may go through each step before submitting your Pull Request.<br> > > <br> > > On 1/12/21 7:52 PM, Kunal Tulsidasani wrote:<br> > > > should test my code (Procedure) after making commits before<br> > > making any<br> > > > pull requests?<br> > > ><br> > > -- Srevin Saju<br> > > <a href="https://srevinsaju.me" rel="noreferrer" target="_blank">https://srevinsaju.me</a> <<a href="https://srevinsaju.me" rel="noreferrer" target="_blank">https://srevinsaju.me</a>><br> > > <br> > -- <br> > Srevin Saju<br> > <a href="https://srevinsaju.me" rel="noreferrer" target="_blank">https://srevinsaju.me</a><br> > <br> <br> pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) <<a href="mailto:srevinsaju@sugarlabs.org" target="_blank">srevinsaju@sugarlabs.org</a>><br> > sub RSA 4096/14479587 2020-05-19<br> > <br> <br> <br> <br> <br> > _______________________________________________<br> > Sugar-devel mailing list<br> > <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> <br> <br> -- <br> James Cameron<br> <a href="https://quozl.linux.org.au/" rel="noreferrer" target="_blank">https://quozl.linux.org.au/</a><br> _______________________________________________<br> Sugar-devel mailing list<br> <a href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> </blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Jui Pradhan</div></div>