Open davelab6 opened 8 years ago
Is this issue resolved , if not I would like to try to resolve this issue.
Should this issue be closed? It looks like the testing part is already been added into the developer documentation
Thanks for pointing this out @Melantha-Chen, I'm thinking of leaving this open as the email referenced in the mailing list archive talks about setting up tests for activities and not the manual testing that's provided in the documentation and at the moment we don't have tests setup for most activities and this might be a good starting point for someone who decides to setup tests for an activity in the future.
@quozl thoughts?
I agree. https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#testing is a checklist for human testing. The 2014 post referenced by the opening comment is about architectural change that would support automated testing and continuous integration. Potentially useful for anyone in future, but I don't see any desire to do it right now with the size we are. I don't mind if anyone takes the challenge, but it is a huge challenge, with very little reward, very little justification (rate of change so low) and won't be easily supported by the other developers. Perhaps the original situation was guidance for students by a professor, having their professional development as part of the equation. It is always good to learn, but our community is not large enough to teach well.
Most of the problems with Sugar and activities do not exist as issues in GitHub, and nor should we expect them to.
http://lists.sugarlabs.org/archive/sugar-devel/2014-January/046700.html explains how to set up test in an Activity, and this should be integrated into the developer documentation