The tests that hit localhost may need their own list, maybe browserIncludes.txt or something like that. When folks run mustella in browser mode, they need to set up an http server pointing at the tests directory and these additional tests should run.
The ones that will be harder to fix are ones that hit the old flexqa server. On 8/30/12 6:20 AM, "Peter Ent" <p...@adobe.com> wrote: > Tests that rely on a local server are currently not supported. However, if > interested individuals want to figure out how to do that, it would make > testing more robust. I think however, the best thing to do is skip this > test and then we can revisit the issue once all the "normal" tests are > working. > > There are two approaches to skipping the test: add the test to the > tests/ExcludeListMac.txt and tests/ExcludeListWin.txt files or comment-out > the test, with a note, in the MXML test file. I personally think the > exclusion file is better since it keeps a list of all of the tests being > excluded in one location, but I don't think there is a provision for > comments; I'm going to take a look at that and see if the Exclusion files > will accept a comment and sent an email shortly. > > --peter > > On 8/30/12 9:13 AM, "Cyrill Zadra" <cyrill.za...@gmail.com> wrote: > >> There's a test in test/Mangers/StyleManager/Versioning that tries to load >> a >> swf from a local server. Do I have to setup server .. or how is this been >> tested in mustella? >> >> <SetProperty target="swf1" propertyName="source" >> value="http://localhost:{portNumber}/Managers/StyleManager/SWFs/assets/MP_ >> customStyles_embeddedImages.swf?port={portNumber}" >> waitTarget="swf1" waitEvent="updateComplete"/> >> >> regards >> cyrill > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
