Features/Add-ons/Add-ons Default to Compatible/TestPlan: Difference between revisions

Jump to navigation Jump to search
Line 35: Line 35:
*Two bugs are RESOLVED on AMO: [https://bugzilla.mozilla.org/show_bug.cgi?id=692971 692971] [https://bugzilla.mozilla.org/show_bug.cgi?id=692972 692972]
*Two bugs are RESOLVED on AMO: [https://bugzilla.mozilla.org/show_bug.cgi?id=692971 692971] [https://bugzilla.mozilla.org/show_bug.cgi?id=692972 692972]


== Status-week 1 beta ==
== Status-week 11/7/2011-11/14/2011 ==


Implementation work has started on Add-on manager side starting with the following bugs:
*[https://bugzilla.mozilla.org/show_bug.cgi?id=693897 Allow addons to opt-in to strict compatibility checking]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=693901 Add preference to globally (re)enable strict compatibility checks]
*[https://bugzilla.mozilla.org/show_bug.cgi?id=693899 Support detecting binary components, and enable strict compatibility checking when found]
TO DO list:
*create 75% basic functionality test cases
*run feature basic functionality test cases on all platforms (Windows XP, Windows 7, Mac OS 10.6, Ubuntu 11.10)
*run feature basic functionality test cases on Firefox 7, 8 and 9, while upgrading from each one to Nightly.
*create test cases for edge areas and different add-on states.
COMPLETED:
*created 75% basic functionality test cases
*ran created basic functionality test cases on Ubuntu 11.10 and Windows XP


== Use Cases to Test ==
== Use Cases to Test ==
938

edits

Navigation menu