607
edits
Changes
Jump to navigation
Jump to search
Line 105:
Line 105: − * Get a buildbot running on at least Fedora and Ubuntu. − * Pylint the core codebase, check regressions in the buildbot, make it a requirement to be pylint clean to submit patches. − * Add basic checks on the buildbot about shell and activity startup. Line 115:
Line 112: − + − + − + − * sugar shell and module are pylint clean and checked by the buildbot.
→Quality assurance
=== Ideas ===
=== Ideas ===
* Integrate sugarbot into sugar-jhbuild and buildbot. Write tests for it and encourage the activity authors to do so too.
* Integrate sugarbot into sugar-jhbuild and buildbot. Write tests for it and encourage the activity authors to do so too.
* Start writing unit tests and use nose to run them into the buildbot. We will have to figure out how to unit test UI code.
* Start writing unit tests and use nose to run them into the buildbot. We will have to figure out how to unit test UI code.
=== Done ===
=== Done ===
* Defined the general goals.
* Get a buildbot running on at least Fedora and Ubuntu. '''(marco)'''
* Work on the buildbot is in progress, but it's already useful.
* Pylint the core codebase, check regressions in the buildbot, make it a requirement to be pylint clean to submit patches. '''(marco)'''
* Zach working on sugarbot integration.
* Add basic checks on the buildbot about shell and activity startup. '''(marco)'''