[Sugar-devel] WANT TO CONTRIBUTE TO SUGAR LABS FOR GSOC 2021

[Jui Pradhan]

Hi,
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.

Check the log files after changes. Log files contain tracebacks....
- for activities see `~/.sugar/default/logs/activity_bundle_id.log`
- for sugar refer to the logs `~/.sugar/default/logs/shell.log`

- 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:
https://github.com/sugarlabs/sugar/blob/master/docs/development-environment.md

Making changes to the Sugar Activities:
Before you make any changes to the source code it is imperative to know how
the activity works without these changes.
While testing lookout for:
- Your code does not make an unintentional change. By that I mean in the
process of solving one issue, you do not create another.
- Design tests and iterate until the tests have sufficient coverage for the
code changes.

As Srevin and James mentioned, there can be more to testing depending on
what part of code you are working on.
I hope our emails help.

Regards,
Jui

On Wed, Jan 13, 2021 at 2:14 AM James Cameron <quozl at laptop.org> wrote:

> I agree, there is no simple explanation for how to test code, as it
> depends exactly on where the change is made.
>
> However, I'm surprised if one would ever reach the point of having to
> test a change without knowing how to run the program that you are
> about to change.  That would be very much going forward blindly.
>
> On Tue, Jan 12, 2021 at 08:19:51PM +0300, Srevin Saju wrote:
> > It would be quite complicated to explain what to check. We would be able
> to
> > explain better if you could send a draft Pull Request and ping me there.
> >
> > Some basic ways to test, common to all activities / sugar / any FOSS
> > software would be to:
> >
> > 1. Clone the source, checkout master
> > 2. Login to Sugar
> > 3. Run the software / activity : (in sugar, it would be to run `python
> >    setup.py install` or `python setup.py dev`, click on the activity's
> >    icon on the Sugar Home view
> > 4. Make your changes, GOTO STEP 2 and repeat those with your new changes.
> > 5. Finally, push your changes when you are satisfied.
> > 6. Have fun.
> >
> > On 1/12/21 8:08 PM, Kunal Tulsidasani wrote:
> > > Thankyou for your reply!
> > >
> > > I have read this file and this shows on what bases to check!
> > >
> > > I want to know how to check? Like what should I do?
> > >
> > > Regards
> > > Kunal
> > >
> > > On Tue, 12 Jan 2021, 22:26 Srevin Saju, <srevinsaju at sugarlabs.org
> > > <mailto:srevinsaju at sugarlabs.org>> wrote:
> > >
> > >     You might be interested in
> > >
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone
> > >     <
> https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#checklist---anyone
> >
> > >
> > >     . You may go through each step before submitting your Pull Request.
> > >
> > >     On 1/12/21 7:52 PM, Kunal Tulsidasani wrote:
> > >     > should test my code (Procedure) after making commits before
> > >     making any
> > >     > pull requests?
> > >     >
> > >     --     Srevin Saju
> > >     https://srevinsaju.me <https://srevinsaju.me>
> > >
> > --
> > Srevin Saju
> > https://srevinsaju.me
> >
>
> pub   RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) <
> srevinsaju at sugarlabs.org>
> > sub   RSA 4096/14479587 2020-05-19
> >
>
>
>
>
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> https://quozl.linux.org.au/
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
Jui Pradhan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20210115/ae4b3799/attachment-0001.htm>