Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Bug 781105 - Bump versions of manifestdestiny=0.5.5 and mozrunner=5.9 and release on PyPI. r=jhammel #29

Closed
wants to merge 2 commits into from

2 participants

@whimboo
Owner

No description provided.

@k0s
Owner

d22b344

One of the reasons I don't like pull request to mozbase is since we don't actually merge them its just one more place that has to be closed that no one remembers

@k0s k0s closed this
@whimboo
Owner

Sorry, that I have missed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Aug 8, 2012
  1. @whimboo
Commits on Aug 10, 2012
  1. @whimboo
This page is out of date. Refresh to see the latest.
View
19 manifestdestiny/README.md
@@ -10,15 +10,14 @@ What ManifestDestiny gives you:
are just dicts with some keys. For example, a test with no
user-specified metadata looks like this:
- [{'path':
- '/home/jhammel/mozmill/src/ManifestDestiny/manifestdestiny/tests/testToolbar/testBackForwardButtons.js',
- 'name': 'testToolbar/testBackForwardButtons.js', 'here':
- '/home/jhammel/mozmill/src/ManifestDestiny/manifestdestiny/tests',
- 'manifest': '/home/jhammel/mozmill/src/ManifestDestiny/manifestdestiny/tests',}]
+ [{'expected': 'pass',
+ 'path': '/home/mozilla/mozmill/src/ManifestDestiny/manifestdestiny/tests/testToolbar/testBackForwardButtons.js',
+ 'relpath': 'testToolbar/testBackForwardButtons.js',
+ 'name': 'testBackForwardButtons.js',
+ 'here': '/home/mozilla/mozmill/src/ManifestDestiny/manifestdestiny/tests',
+ 'manifest': '/home/mozilla/mozmill/src/ManifestDestiny/manifestdestiny/tests/manifest.ini',}]
-The keys displayed here (path, name, here, and manifest) are reserved
-keys for ManifestDestiny and any consuming APIs. You can add
-additional key, value metadata to each test.
+The keys displayed here (path, relpath, name, here, and manifest) are reserved keys for ManifestDestiny and any consuming APIs. You can add additional key, value metadata to each test.
# Why have test manifests?
@@ -110,8 +109,8 @@ Manifest Destiny gives tests as a list of dictionaries (in python
terms).
* path: full path to the test
-* name: short name of the test; this is the (usually) relative path
- specified in the section name
+* relpath: relative path starting from the root manifest location
+* name: file name of the test
* here: the parent directory of the manifest
* manifest: the path to the manifest containing the test
View
2  manifestdestiny/setup.py
@@ -14,7 +14,7 @@
description = ''
PACKAGE_NAME = "ManifestDestiny"
-PACKAGE_VERSION = "0.5.4"
+PACKAGE_VERSION = '0.5.5'
setup(name=PACKAGE_NAME,
version=PACKAGE_VERSION,
View
2  mozrunner/setup.py
@@ -7,7 +7,7 @@
from setuptools import setup
PACKAGE_NAME = "mozrunner"
-PACKAGE_VERSION = '5.8'
+PACKAGE_VERSION = '5.9'
desc = """Reliable start/stop/configuration of Mozilla Applications (Firefox, Thunderbird, etc.)"""
# take description from README
Something went wrong with that request. Please try again.