Features/Jetpack/Add-on SDK Debugging

From MozillaWiki
Jump to navigation Jump to search
Please use "Edit with form" above to edit this page.

Status

Add-on SDK Debugging
Stage Draft
Status `
Release target `
Health OK
Status note Sorely, sorely needed. Somebody... please... help... us!

{{#set:Feature name=Add-on SDK Debugging

|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=Sorely, sorely needed. Somebody... please... help... us! }}

Team

Product manager David Mason
Directly Responsible Individual `
Lead engineer `
Security lead `
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

{{#set:Feature product manager=David Mason

|Feature feature manager=` |Feature lead engineer=` |Feature security lead=` |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature additional members=` }}

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

` {{#set:Feature open issues and risks=` |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

|Feature users and 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. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

Priority Unprioritized
Rank 999
Theme / Goal `
Roadmap Jetpack
Secondary roadmap `
Feature list Jetpack
Project `
Engineering team Jetpack

{{#set:Feature priority=Unprioritized

|Feature rank=999 |Feature theme=` |Feature roadmap=Jetpack |Feature secondary roadmap=` |Feature list=Jetpack |Feature project=` |Feature engineering team=Jetpack }}

Team status notes

  status notes
Products ` `
Engineering ` `
Security ` `
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=` |Feature security health=` |Feature security notes=` |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}


Retrieved from "https://wiki.allizom.org/index.php?title=Features/Jetpack/Add-on_SDK_Debugging&oldid=659746"