Features/Jetpack/Add-on SDK Debugging

Status

Team

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Debugging in the SDK is currently console.log, i.e. printf. Debugging in software development has come a long way since printf, and just as the Web Developer Tools team is building great web application debugging into Firefox

Feature set might include:

• Introspection
• Memory profiling
• Setting breakpoints
• Stepping through code
• Add-on performance measurement
• Add-on start-up time measurement

• about:addons having a "debug" button that might bring up a console,

 etc

2. Users & use cases

The target audience is addon developers. The use case is an add-on developer using the Add-on SDK (either directly or via the Add-on Builder) to build an addon.

Any debugging tools we build should resemble what it is like to debug other Mozilla projects. Therefore it is imperative that we work closely with the dev tools team to make sure that these tools are part of the greater package of Firefox debugging.

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

8. Reviews

Security review

`

Privacy review

`

Localization review

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes