Closed Bug 693547 Opened 13 years ago Closed 10 years ago

Add test-run for structural tests (developers, back-end tests)

Categories

(Mozilla QA Graveyard :: Mozmill Automation, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: whimboo, Unassigned)

References

Details

(Whiteboard: [mentor=whimboo][lang=py])

As talked about on the automation mailing list (http://groups.google.com/group/mozilla.dev.automation/browse_thread/thread/87ee0df55e647e28#) we need a new test-run for Mozmill tests written by developers. We decided to name this test-run 'structural' for the time being. The future will show if it's the right name or if we will have to change it later on.
Depends on: 693306
Whiteboard: [mentor=whimboo][lang=py]
Just to add some specs:

1. Each individual test in this testrun should run in isolation mode. That's the only situation other test frameworks like Mochitests can't handle. For an example allow a test do some preparation work before Firefox gets started. It can be a python callback from the automation scripts back to the appropriate test folder in mozmill-tests.

2. The binary has to be backed-up and restored between each test if modifications have been done.

3. We should allow non-restart and restart tests

Would we need anything else? Mike would those steps satisfy your needs for autoconfig tests?
I believe this should work.

My requirements are:

Copy firefox.cfg to location of EXE
Copy autoconfig.js to defaults/preferences directory.
Run Firefox and execute the test.
Then those files would need to be removed for any further testing.
(In reply to Michael Kaply (mkaply) from comment #2)
> Copy firefox.cfg to location of EXE
> Copy autoconfig.js to defaults/preferences directory.

That will be fulfilled. The callback handler will get the application folder as parameter. 

> Run Firefox and execute the test.
> Then those files would need to be removed for any further testing.

We will delete the binary directory and replace it with the backup we have made before.

Sadly I will not have the time to work on it in the next foreseeable future. But I would be happy to mentor someone who want to take this.
This issue is tracked as https://github.com/mozilla/mozmill-automation/issues/147 now.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.