Kitchensink App

The purpose of Kitchensink's existence is to test web APIs directly on the device. App might be installed in FirefoxOS device (or simulator) and on Android vie Firefox browser. This is a privileged app. It can't test certified APIs.

Current status

Version uploaded to the Marketplace is a little behind the repository one. The latter has implemented sending results to the Collection Server. This is implemented in Django and there are issues in running the server side from PAAS. There is an idea to rewrite the KitchenSinkServer to a platform whih runs easily from PAAS, potentially NodeJS.

Questions

Certified APIs?

Is testing if certified API is callable useful? Or would it be better to remove them entirely from UI?

Developer info

App is using Mootools Prime to provide class-like structure.

• How tests are run Kitchensink App/APITestStructure
• Tested APIs Kitchensink App/TestedAPIs
• Settings module description Kitchensink App/Settings
• Collecting data Kitchensink App/CollectingServer

ToDo

• Run collection server from PAAS
• Use templates (currently HTML is written inside the model which is ugly and troublesome)
• Implement new UI (depends on templates)
• Create front-end for collected data
• Find a way to identify model and OS version for collecting data. This requires FxOS cooperation. We rely on the userAgent only

Links

• Main repository - https://github.com/mozilla/KitchenSink/
• Collection server repository - https://github.com/mozilla/KitchenSinkServer
• Marketplace - https://marketplace.firefox.com/app/kitchensink/