Auto-tools/Projects/Loderunner: Difference between revisions

Jump to navigation Jump to search

Auto-tools/Projects/Loderunner (view source)

Revision as of 19:57, 19 May 2010

584 bytes removed ,  19 May 2010
no edit summary
No edit summary
No edit summary
Line 84: Line 84:
= Some Non-Goals =
= Some Non-Goals =
* We don't want to support every nuance of the existing harnesses in these components.  This API should be extensible enough to support those harnesses but not so that it is hamstrung by supporting them.   
* We don't want to support every nuance of the existing harnesses in these components.  This API should be extensible enough to support those harnesses but not so that it is hamstrung by supporting them.   
= Next Steps =
* Did I define the components properly?
** Are any missing?
** Are there smaller building blocks that these can be broken into that makes sense?
* What are the interfaces on each of these components?
** How are the components extended?
** How are those interfaces consumed?
** How will those interfaces be denoted in Python (which I assume most of this will be implemented in) - since python has no concept of "public" versus "private" what code convention will we use to differentiate the two?
* How will the components be packaged?
** Should each one be callable from the command line as its own tool in as much as it makes sense (for instance the profilemanager might be useful this way.  The command line manager might not be).
** Should we require packaging?  Can co-location in directories work?


= Plan =
= Plan =
Line 105: Line 91:
# Code the API use into a set of tests
# Code the API use into a set of tests
# Code the interfaces and the modules.
# Code the interfaces and the modules.
# Determine packaging solution for these components - some might want to be command line tools (profile manager comes to mind), co-location in directories might work, but providing reusable python modules might also be a good strategy)
# Integrate said modules into the existing harnesses, refactoring specialized data as needed (and moving basic functionality into these components where appropriate)
# Integrate said modules into the existing harnesses, refactoring specialized data as needed (and moving basic functionality into these components where appropriate)
# Profit!
# Profit!
Ctalbert
Confirmed users
3,816

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/224364"

Navigation menu