Auto-tools/Projects/Mozmill/Mozmill 2.0/JsBridge

< Auto-tools‎ | Projects‎ | Mozmill‎ | Mozmill 2.0
Revision as of 23:25, 4 January 2011 by Ctalbert (talk | contribs) (Created page with "JsBridge refactoring will give us much more control over what tests are run and how they are run. It will also enable us to more easily maintain and change the event structure t...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

JsBridge refactoring will give us much more control over what tests are run and how they are run. It will also enable us to more easily maintain and change the event structure that talks between JS and Python. This is the set of things that need to be done:

  • Expose log message to JS test runner module
    • make logging work even if no --log option specified
  • Create abstraction mapping JSObjects so that you have a real interface
  • Create ability for test to specify the next test to run
  • Remove standalone JSbridge CLI
  • Create einterface around jsbridge so we can decouple jsbridge from mozmill.
  • Clean up the data fed back to python for nice output in logging (stretch goal)
  • Ensure listener arch is robust and modifyiable
  • Ensure when tests are skipped entire test can be skipped instead of a test step