Testing infrastructure change: ManifestDestiny - manifestparser

2014-06-11 Thread William Lachance
Just wanted to make a quick announcement that ManifestDestiny, the 
python package we use internally here at Mozilla for declaratively 
managing lists of tests in Mochitest and other places, has been renamed 
to manifestparser. We kept the versioning the same (0.6), so the only 
thing you should need to change in your python package dependencies is a 
quick substitution of “ManifestDestiny” with “manifestparser”. We will 
keep ManifestDestiny around indefinitely on pypi, but only to make sure 
old stuff doesn’t break. New versions of the software will only be 
released under the name “manifestparser”.


Quick history lesson: “Manifest destiny” refers to a philosophy of 
exceptionalism and expansionism that was widely held by American 
settlers in the 19th century. The concept is considered offensive by 
some, as it was used to justify displacing and dispossessing Native 
Americans. Wikipedia’s article on the subject has a good summary if you 
want to learn more.


Here at Mozilla Tools  Automation, we’re most interested in creating 
software that everyone can feel good about depending on, so we agreed 
decided to rename it. When I raised this with my peers, there were no 
objections. I know these things are often the source of much drama in 
the free software world, but there’s really none to see here.


Happy manifest parsing!

Will
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: ManifestDestiny

2013-03-19 Thread jmaher
On Tuesday, March 19, 2013 5:37:22 AM UTC-4, Robert O'Callahan wrote:
 Cool name. However, are you actually proposing replacing, say, the reftest 
 manifest format with this format? It looks like it would be a lot more
 verbose.

My understanding is there is no need or plan to replace the reftest manifest 
format with ManifestDestiny.  Right now this is used for xpcshell, and we are 
working towards making it work for mochitests.  

Trying to make a one size fits all solution doesn't really make sense for all 
of the different harnesses.  The reftest .list format is too clunky for just 
listing out tests to run, likewise the ManifestDestiny .ini format is too 
awkward to list A vs B type of comparisons along with complex conditions.

-Joel
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform