Changes

Jump to: navigation, search

Project List

5 bytes added, 16:23, 16 November 2006
Moved JS Ref to Inactive list, spelling fixes
Reference: http://cs.senecac.on.ca/fsoss/2006/workshop.html#XULRunner
 
=== [[Updating JS guide and JS reference]] ===
 
The current [http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Guide JavaScript guide] and [http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference reference ] are valuable, but in serious need of updating in both structure and content (new language features, more relevant compatibility information, improved examples).
 
Related tech and skills: documentation, JavaScript
=== [[Airbag development and server operation]] ===
=== [[MDC Infrastructure]] ===
Intergrate Integrate new features to MDC, work on existing bugs and fix compatibility issues for the upgrade of Mediawiki to 1.7. (Tentative description)
=== [[Firefox Performance Testing : A Python framework for Windows]] ===
=== [[Source Code Indexing Service Analysis]] ===
 
Mozilla is evaluating Subversion for revision control, and at the same time wants to look at other source indexing services. This project will setup, document, and test other potential services (e.g., fisheye, opengrok, mxr) on one of the Seneca-Mozilla servers. In each case this requires configuration changes and some scripting to get the services to properly integrate with Mozilla’s other on-line tools. When the test services are installed and synched with the live source tree, Mozilla will point its developers to them and get feedback—-the students will help collect and synthesize this feedback.
=== [[Firefox Performance Testing : A Python framework for Windows | Performance Testing]] ===
Extending the performance tookit toolkit and tinderbox reporting system. The project begins with a framework for testing pageloads page loads and startup times in Win32. The successful completion of this project will see this framework develop into a more robust system complete with processor-timing information and graphing. Memory analysis and samples during runs would also be beneficial. Further success or subprojects sub-projects could include porting the system Linux and OS X platforms.
Reference: [https://bugzilla.mozilla.org/show_bug.cgi?id=346785 Bug 346785]. Work with Mozilla's Rob Campbell and Jay Patel from the QA Team.
Reference: See https://despot.mozilla.org/help.html and http://lxr.mozilla.org/mozilla/source/webtools/despot/README. Also, please speak with [[User:Reed|Reed Loden]] (reed) about this project.
 
=== [[Updating JS guide and JS reference]] ===
 
The current [http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Guide JavaScript guide] and [http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference reference ] are valuable, but in serious need of updating in both structure and content (new language features, more relevant compatibility information, improved examples).
 
Related tech and skills: documentation, JavaScript
 
=== [[Bugzilla component-watching]] ===
=== Automated Testing ===
Programmatically Pro grammatically driving the browser to perform human-like tasks repeatedly. The programmer will have to create a framework for driving browser components in JavaScript or other scripting language to repeatedly test various pieces of the application. Ideally, the successful completion of this task will see a test or suite of tests that can be invoked by command line to start the browser, run the test suites and then exit and record the results for display or analysis.
Reference: Work with Mozilla's Rob Campbell and Jay Patel from the QA Team.

Navigation menu