748540 - required test path for a11y mochitests is confusing

Status: NEW

(Core :: Disability Access APIs, defect)

Description

[Trevor Saunders (:tbsaunde)]

currently if you want to run say accessible/tests/mochitest/relations/test_general.html the proper test path is accessible/relations/test_general.html this is shorter than the actual path in the tree which is nice, but it confuses people who don't know it (Kyle complained about it a week ago, and a contributor asked how to run a single test today).

depending on what we want to do with the crash tests sub directory that is afaik currently unused we could rename accessible/tests/mochitest/blah to accessible/test/blah and change the make files to install to $(WHAT_EVER)/accessible/test/blah which wouldn't be much longer and in line with the path in the tree and what people expect.

Comment 1

[alexander :surkov (:asurkov)]

personally I'm distracted of pointing 'accessible' in the path. I would like to be able to do:
python runtests.py --a11y --test-path=relations/test_general.html

iirc we can do nothing about crashtests until they allow privileges for accessibility running.

Comment 2

[Trevor Saunders (:tbsaunde)]

(In reply to alexander :surkov from comment #1)
> personally I'm distracted of pointing 'accessible' in the path. I would like
> to be able to do:
> python runtests.py --a11y --test-path=relations/test_general.html

that seems nice,   but I wonder if it'll trip up new people or people who don't run them all the time.

> iirc we can do nothing about crashtests until they allow privileges for
> accessibility running.

Well, if we can run them with non default prefs set we could get a11y on that way, or maybe we could expose a function to content js only in test only builds that alows content to turn a11y on?

Comment 3

[alexander :surkov (:asurkov)]

(In reply to Trevor Saunders (:tbsaunde) from comment #2)
> (In reply to alexander :surkov from comment #1)
> > personally I'm distracted of pointing 'accessible' in the path. I would like
> > to be able to do:
> > python runtests.py --a11y --test-path=relations/test_general.html
> 
> that seems nice,   but I wonder if it'll trip up new people or people who
> don't run them all the time.

this is rather documentation issue. But could we support both ways if some people find this way confusing?

> > iirc we can do nothing about crashtests until they allow privileges for
> > accessibility running.
> 
> Well, if we can run them with non default prefs set we could get a11y on
> that way, or maybe we could expose a function to content js only in test
> only builds that alows content to turn a11y on?

We need to move discussion to proper bug. I was able to find bug 481587 but it says nothing about permissions.