898374 - Move mutt tests from js/frame/restart/states into the python tests folder

Status: RESOLVED WONTFIX

(Testing Graveyard :: Mozmill, defect)

Description

[Andreea Matei [:AndreeaMatei]]

We want to move the tests inside mutt/mutt/tests/js/frame/restart/states in the python tests side, most likely in js-modules.

This is regarding mozmill 2.0, you can clone it from here:
https://github.com/mozilla/mozmill

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Before we want to move those tests please check what's already covered by the Python state machine test. Most is probably covered and we would have to enhance the py test.

Comment 2

[allen0crade]

Hi, I am interested and willing to work on this. It would be great if you can provide me all the all links to mozmill installation, usage and development instructions.


Thanks

Comment 3

[Andreea Matei [:AndreeaMatei]]

Hi Allen, thanks for your interest in this bug.

In this bug we need to work with Mozmill 2.0, is a new version in development, here's a link to use it:
https://github.com/mozilla/mozmill

Regarding how to run tests under mozmill:
https://developer.mozilla.org/en-US/docs/Mozmill_Tests

I'm quickly checking what's already covered by the state machine test and come back with steps for you to fix this bug. Let me know if you have questions or issues with your mozmill 2.0 usage.

Comment 4

[allen0crade]

Hi Andreea, 

I have followed the instructions to install mozmill (https://developer.mozilla.org/en-US/docs/Mozmill_Tests) but these tests only work for the mozmill 1.5.x.

Can you give me step by step instructions to run mozmill tests for mozmill 2.0.

Thank you

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Andreea, can you please get back to allen0crade? Thanks!

Comment 6

[Andreea Matei [:AndreeaMatei]]

Sorry Allen it took so long.
Just to make sure, mozmill --v shows you Mozmill 2.0? 

The tests in the repository work in 1.5 and 2.0 as well, you just have to make sure you're using the right mozmill. That is why I gave you this link for you to clone and install it in a virtual env:
https://github.com/mozilla/mozmill

If you do have 2.0 working, just clone the repository:
hg clone http://hg.mozilla.org/qa/mozmill-tests

and run a test with mozmill -t PATH_TO_A_TEST -b PATH_TO_FIREFOX
Be aware --show-errors/--show-all does not apply on 2.0.

If you encounter issues, please add the command you ran and the output to pastebin.mozilla.org and add the link here to be able to help.
This is for your setup, because the bug is regarding the mutt tests from mozmill 2.0, not the ones in mozmill-tests:
https://github.com/mozilla/mozmill/tree/master/mutt/mutt/tests

Thanks!

Comment 7

[Manish Goregaokar [:manishearth]]

Anvesh, do you think that you can try this? :whimboo in #automation can help if needed.

Comment 8

[Manish Goregaokar [:manishearth]]

(If this is too hard, try bug 656633, or ping me in IRC)

Comment 9

[Faisal Anees]

Hi !! I would like to work on this bug. I have done what :AdreaaaMatei has suggested and the tests are working fine, no issues. I have a doubt, is this bug all about moving test files from one directory to another ??

Comment 10

[Faisal Anees]

Please assign me this bug

Comment 11

[Henrik Skupin [:whimboo][⌚️UTC+1]]

To accomplish the goal of this bug it is not enough to simply move the files over to the test/py folder. You will also have to create a Python test beside the ones already exist. Especially have a look at the existing restart Python tests. It has to run all the js files as pointed out on this bug, and afterward it has to check if all the tests have been executed. Only that way we can be sure that all the tests have been run (even in the right order).

Oh, and thanks for your interest on this bug!

Comment 12

[Henrik Skupin [:whimboo][⌚️UTC+1]]

No progress has been made on this bug. So I'm going to unassign you from it.

Also Mozmill will reach its end of life soon. We are currently working on getting all the tests for Firefox ported to Marionette. For status updates please see bug 1080766.