487755 - [mozmill] Testscripts from MozMill TestDay

Status: VERIFIED FIXED

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Description

[Aakash Desai [:aakashd]]

Add your testscript as an attachment!

Make sure to name the attachments as the following: "username_litmusSubgroup_TestCase#.js"

This is so we'll be able to identify who wrote which testscript and figure out who to send t-shirts to at the end of the event!

Happy Scripting!

Comment 1

[cmtalbert]

Attachment: Test Template for Test Writing

This is a test template.  To use it, copy and paste it into Mozmill or download it to your computer and open it in Mozmill using File->Open.  

* Be sure to replace "Your Name" with your actual name in the license header block.  This is the standard Mozilla license header and you'll be remembered in our source tree as long as this test is there.
* The actual test part is below the license header, and all it does is open a browser controller and navigate to http://www.google.com.  Feel free to rename the test function to something other than "testFoo" and add in your test code inside that function.

Comment 2

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testBackandForward.js

Comment 3

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testHomeButton.js

Comment 4

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testStopandReload.js

Comment 5

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testStopandReload.js

Comment 6

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testGoogleSuggestedTerms.js

Comment 7

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testBackandForward.js

Comment 8

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testHomeButton.js

Comment 9

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testStopandReload.js

Comment 10

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: JMaher - downloading: opening the downloads dialog (litmus #5936)

please review attached testcase and add to repository

Comment 11

[cmtalbert]

Attachment: merike's test for calendar

Comment 12

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: JMaher - downloading: closing the downloads dialog (litmus #5937)

Comment 13

[Heather Arthur [:harth]]

Attachment: Harthur : set home page to current page (litmus #5921)

Comment 14

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

Comment on attachment 372112 [details]
AakashDesai_General_testGoogleSuggestedTerms.js

In general I miss the complete license plate.

>var testGoogleSuggestedTerms = function () {

Please add a comment before the function which points to the existing Litmus test. See:
http://hg.mozilla.org/qa/mozmill-tests/file/fd0cd7b00bdd/firefox/bookmarks/test_addBookmarkToMenu.js#l55

>  //Open the Google Webpage

One space behind the // chars and "web page"

>  controller.open("http://www.google.com/");

You should better use http://www.google.com/webhp?complete=1&hl=en here. Otherwise users will be redirected to the language depending on there geo location.

>  controller.waitForPageLoad();
>  
>  //Activate the search bar and input in a search parameter
>  controller.click(new elementslib.Name(controller.tabs.activeTab, "q"));

You should better wait for existence of this textbox before operating on it. Probably we should add a module and transfer my delayedClick function over there for now. I'll check it. Further you don't have to use the click call. Calling type is enough.

>  controller.type(new elementslib.Name(controller.tabs.activeTab, "q"),"area");
>  controller.sleep(200);

Missing space before the search term and make the sleep a bit longer so we will have a visual indicator and are on the safe side that suggestions have really be loaded.

>  //Look for the first element in the drop down table and enable the search

I would propose "Click the first element in the suggestion auto-complete popup and start the search"

>  //Check if Search page has come up
>  controller.waitForElement(new elementslib.Name(controller.tabs.activeTab, "q"));
>  controller.waitForElement(new elementslib.Link(controller.tabs.activeTab, "Next"));

I think we should better check if the textbox (q) on the web page contains the selected search term from above now.

Comment 15

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

Comment on attachment 372115 [details]
AakashDesai_General_testBackandForward.js

> * The Initial Developer of the Original Code is
> * ____________________Aakash Desai____________________.

Remove the underlines. They were only a placeholder to indicate where to put your name.

>var testBackandForward = function() {

Please add a comment in-front of the function too.

>  index=0;
>  
>  //Open up the list of websites statically assigned in the array
>  while (index<websites.length) {
>  controller.open(websites[index]);
>  controller.waitForPageLoad();
>  index++;
>  }

Please use a for loop here and obey the indentation.

>  //Click on the Back button for the number of websites visited
>  for (var i=0;i<websites.length;i++) {
>  controller.goBack();
>  controller.waitForPageLoad();
>  }
>  
>  //Click on the Forward button for the number of websites visited
>  for (var j=0;j<websites.length;j++) {
>  controller.goForward();
>  controller.waitForPageLoad();
>  }

Please reuse index here. It will be more obvious. Further check for a major element on each page which will probably not changed/removed. Otherwise we will not know if the former/next page has really be loaded.

Comment 16

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

(In reply to comment #8)
> Created an attachment (id=372116) [details]
> AakashDesai_General_testHomeButton.js

This test is already covered by Tracy on bug 479500. Please check with him who will handle this. Afterward ask for review.

Comment 17

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

Comment on attachment 372117 [details]
AakashDesai_General_testStopandReload.js

> * ____________________Aakash Desai____________________.

Remove the underscore here too.

>var testStopandReload = function() {

Please add a comment before the function too. See my last replies.

>  //Go to the NYPost front page and stop it before it fully loads
>  controller.open("http://www.nypost.com/");
>  controller.sleep(100); /* A short wait for the url to be loaded onto the browser*/
>  controller.click(new elementslib.ID(controller.window.document, "stop-button"));

You can safely set the sleep to 1000 and after clicking stop you should check for an element at the bottom of the page. It should throw as expected. 

>  //Reload the NYPost front page and wait for it to completely load
>  controller.refresh();
>  controller.waitForPageLoad();

Check for the same element here too. Now it has to exist after the page has been loaded.

Comment 18

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

Comment on attachment 372118 [details]
JMaher - downloading: opening the downloads dialog (litmus #5936)

>//
>//contributor: Joel Maher ([e-mail])
>//
>//mozmill automation for litmus testcase 5936 (https://litmus.mozilla.org/show_test.cgi?id=5936)
>//
>//NOTE: this was developed and tested on Mac OS X

Joel, I miss the official license plate. See the template how you have to use it.


>//sleep time necessary to wait for dialog to launch/close
>var sleeptime = 1000;

Can you insert a space before the sleep in the comment? Please use camel case too - sleepTime. When we w

>var testDownloadManagerLaunch = function() {

Please add the above xref to the litmus testcase as comment in-front of the test function. See:
http://hg.mozilla.org/qa/mozmill-tests/file/fd0cd7b00bdd/firefox/bookmarks/test_addBookmarkToMenu.js#l55

>  controller.menus.Tools["Downloads"].click();

Please don't use the labels. We wanna be able to run the test on localized versions too. Use the ids instead:
http://mxr.mozilla.org/mozilla-central/source/browser/base/content/browser-menubar.inc#555

>  var controllerD = mozmill.getDownloadsController();
>  controllerD.assertNode(new elementslib.ID(controllerD.window.document, "clearListButton"));
>  var element_downloadDialog = new elementslib.ID(controllerD.window.document, "downloadManager");
>  controller.keypress(element_downloadDialog, 27, false, false, false, false);
>  controller.sleep(sleeptime);

Can you please put those lines into a function. You are using it four times in this module.

>  var controllerD = mozmill.getDownloadsController();

Gna, why does this function open the download manager window? It's not called new. That looks like a bug and makes it impossible to catch a non-working shortcut. Mikeal, I don't think that this is expected?

>  if (platform == "Win32" || platform == "Linux i686") {
>    controller.keypress(element_browser, "J", true, false, false, false);

Linux uses Ctrl+Shift+Y. Further call os.getPlatform() to get the platform where the test runs.

>  else {
>    controller.keypress(element_browser, "J", false, false, false, true);
>  }

Only running this code doesn't open the download manager.

>var testDownloadManagerToForeground = function() {

>  //launch download manager and move to background
>  controller.menus.Tools["Downloads"].click();
>  controller.sleep(sleeptime);
>  controller.window.focus();
>  controller.sleep(sleeptime);
>  
>  //test navigation menu to bring to foreground
>  controller.menus.Tools["Downloads"].click();
>  controller.sleep(sleeptime);
>  var controllerD = mozmill.getDownloadsController();
>  controllerD.assertNode(new elementslib.ID(controllerD.window.document, "clearListButton"));
>  var element_downloadDialog = new elementslib.ID(controllerD.window.document, "downloadManager");

Why don't you create not only one test? Everything can be done this way. No need to have two separate tests in this module.

Comment 19

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

(In reply to comment #11)
> Created an attachment (id=372124) [details]
> merike's test for calendar

Clint, that one should be reviewed by yourself. I don't know anything about calendar.

Comment 20

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

Comment on attachment 372164 [details]
JMaher - downloading: closing the downloads dialog (litmus #5937)

This test is already automated by a chrome test:
http://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/downloads/tests/chrome/test_close_download_manager.xul

Joel, at least you can incorporate everything into your first download manager test. There is also a need to close the download manager window. No need to have two different test modules.

Comment 21

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

Comment on attachment 372167 [details]
Harthur : set home page to current page (litmus #5921)

Heather, this test is already in the works by Tracy on bug 479500. You should talk to him how you can merge both efforts.

Comment 22

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: updated test script cleaned up as per feedback from whimboo

Still need to test this on linux/windows.  Also, need the CMD+J to work for Mac OSX.

Comment 23

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: JMaher - downloading: opening the downloads dialog (litmus #5936)

this is the updated version of litmus testcase 5936.  There is no more keyboard shortcuts, an updated license and the use of ID's only.

Comment 24

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

(In reply to comment #18)
> >  var controllerD = mozmill.getDownloadsController();
> 
> Gna, why does this function open the download manager window? It's not called
> new. That looks like a bug and makes it impossible to catch a non-working
> shortcut. Mikeal, I don't think that this is expected?

Filed as bug 488313.

Comment 25

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

Comment on attachment 372641 [details]
JMaher - downloading: opening the downloads dialog (litmus #5936)

>function closeDownloadManager() {
>  var controllerD = mozmill.getDownloadsController();

Can you move the mozmill.getDownloadsController to the main function and supply it via parameter? So we only have to get it once.

>  var element_downloadDialog = new elementslib.ID(controllerD.window.document, "downloadManager");

Why not calling it downloadManager?

>function verifyDownloadManager() {
>  controller.sleep(sleepTime);
>  var controllerD = mozmill.getDownloadsController();

Same here. Supply the controller via parameter.

>  //assuming that clearList button means we are on the downloads dialog
>  controllerD.assertNode(new elementslib.ID(controllerD.window.document, "clearListButton"));

We probably have to wait until getDownloadsController is fixed. I believe we will get back a non-controller so it should be simplier. For now lets check for "downloadManager" instead.

> *  Testcase ID #5936 - Downloading: opening the downloads dialog (NOTE: this does not use the keyboard shortcuts)

Can you please move any additional notes to a second line?

>  var platform = os.getPlatform();
>  var element_browser = new elementslib.Lookup(controller.window.document, '/id("main-window")/id("navigator-toolbox")/id("nav-bar")/id("urlbar-container")/id("urlbar")/anon({"class":"autocomplete-textbox-container"})/anon({"anonid":"textbox-input-box"})/anon({"anonid":"input"})');

That should be removed completely. Not needed anymore.

>  controller.click(new elementslib.Elem(controller.menus.Tools.menu_openDownloads));

"Tools" is a label too.

>  controller.sleep(sleepTime);
>  verifyDownloadManager();

Why we are waiting two times here? Remove this sleep or the one from verifyDownloadManager.

>  //test navigation menu to bring to foreground

That comment should be clearer.

>  controller.click(new elementslib.Elem(controller.menus.Tools.menu_openDownloads));
>  verifyDownloadManager();

Use the id here too. And we probably need a sleep too just to be safe.

And further add a space behind '//' before the comment starts.

Otherwise it looks good. Seems to be the last round now. Thanks!

Comment 26

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: JMaher - downloading: opening the downloads dialog (litmus #5936)

updated testcase with :whimboo's r- comments fixed.

Comment 27

[Joel Maher ( :jmaher ) (UTC -8)]

Attachment: JMaher - downloading: opening the downloads dialog (litmus #5936)

updated with private version of getDownloadManager which doesn't open up dialog if it doesn't previously exist.  Submitted for final review.

Comment 28

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testBackandForward.js

Post Review Changes made

Comment 29

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testGoogleSuggestedTerms.js

Post review changes made

Comment 30

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testStopandReload.js

Post review changes made

Comment 31

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testHomeButton.js

Comment 32

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

Comment on attachment 372872 [details]
JMaher - downloading: opening the downloads dialog (litmus #5936)

Stealing review...

Comment 33

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

Comment on attachment 372872 [details]
JMaher - downloading: opening the downloads dialog (litmus #5936)

Joel sorry, but it will not be the last cycle. I missed some important stuff. :/

>// sleep time necessary to wait for dialog to launch/close
>var sleepTime = 1000;
>var ESC_KEY = 27;

>function closeDownloadManager(controllerD) {
>  var downloadManager = new elementslib.ID(controllerD.window.document, "downloadManager");
>  controller.keypress(downloadManager, ESC_KEY, false, false, false, false);
>  controller.sleep(sleepTime);
>}

We need this only once now. Can you move it back to the main test? And test afterward if the download manager has really be closed. See below how to do that.

>/*

Please use '/**' to be conform with jsdoc.

>  var platform = os.getPlatform();

Ok, I'll mention it a 3rd time now. We don't need this. Please remove it.

>//  var controllerD = getDownloadsController();

Remove that unnecessary line.

>  var controllerD = new mozmill.controller.MozMillController(mozmill.utils.getWindowByTitle("Downloads"));

Damn, this doesn't work on localized builds. We cannot try to get the window by its title. We have to use the windowtype instead.

var window = mozmill.wm.getMostRecentWindow('');
if (window.document.documentElement.getAttribute("windowtype") != "Download:Manager") {
  throw "Download Manager not in foreground";
}

It should be moved to verifyDownloadManager and return the window which was found.

>  // bring download manager to foreground, verify and close
>  controller.click(new elementslib.Elem(controller.menus['tools-menu'].menu_openDownloads));
>  verifyDownloadManager(controllerD);

We cannot do the verification that way. It will always pass even with the download manager window in the background. Check for the front-most window again - same way as we did above. Just call verifyDownloadManager.

Comment 34

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

Comment on attachment 372888 [details]
AakashDesai_General_testBackandForward.js

> * The Initial Developer of the Original Code is
> * Aakash Desai.

It's not you. It's Mozilla Corporation. See:
http://hg.mozilla.org/qa/mozmill-tests/file/4e73e34dd592/firefox/bookmarks/test_addBookmarkToMenu.js

>// Litmus test case: https://litmus.mozilla.org/show_test.cgi?id=5990
>var testBackandForward = function() {

Please use this format:
http://hg.mozilla.org/qa/mozmill-tests/file/4e73e34dd592/firefox/bookmarks/test_addBookmarkToMenu.js#l55

>  var websites=['http://www.espn.com','http://yahoo.com'];

Please add spaces according the code writing guideline of Mozilla. This also applies to a couple of other instances.

>  var pageElements=['searchString','searchsubmit'];

Could you please combine it with the websites array to a 2D array? That will be less error-prone.

elementslib.ID(controller.tabs.activeTab,pageElements[k]),6000,3000);

Why an interval of 3000ms? Leave it alone or specify 100 to speed up the check.

>  // Click on the Back button for the number of websites visited
>  for (var i=0;i<websites.length;i++) {
>  	controller.goBack();
>  	controller.waitForElement(new elementslib.ID(controller.tabs.activeTab,pageElements[websites.length-i-1]),6000,3000);

Please go backward through the array. 

>  	controller.sleep(200); // command does not respond unless there's a small interval in between pageElement and goBack

Please add this comment above the line.

>  //Click on the Forward button for the number of websites visited
>  for (var j=0;j<websites.length;j++) {
>  	controller.goForward();
>  	controller.waitForElement(new elementslib.ID(controller.tabs.activeTab,pageElements[j]),6000,3000);
>  	controller.sleep(200); // command does not respond unless there's a small interval in between pageElement and goForward 
>  }

This is the same code as we have above. It would be great to turn it into a separate function so we could re-use it at a later stage in other tests or move it to a utils module.

Comment 35

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

Comment on attachment 372889 [details]
AakashDesai_General_testGoogleSuggestedTerms.js

There are a couple of things (license plate, coding style, comments) which have to be fixed according to my lastest review.

>  // Open the Google Webpage
>  controller.open("http://www.google.com/webhp?complete=1&hl=en");
>  controller.waitForPageLoad();
>  
>  // Activate the search bar and input in a search parameter
>  controller.click(new elementslib.Name(controller.tabs.activeTab, "q"));
>  controller.type(new elementslib.Name(controller.tabs.activeTab, "q"),"area");

I miss the waitforElement call before clicking the textbox. Btw. you can directly call the type function which will automatically execute a click.

>  // Check if Search page has come up
>  controller.waitForElement(new elementslib.Name(controller.tabs.activeTab, "q"));
>  controller.waitForElement(new elementslib.Link(controller.tabs.activeTab, "Next")); 

I miss the correction of my statement here. Any reason you haven't updated it?

Comment 36

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

Comment on attachment 372890 [details]
AakashDesai_General_testStopandReload.js

Aakash, have you made any update to the test according to my last review? I can only see the license plate update.

Comment 37

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

Comment on attachment 372894 [details]
AakashDesai_General_testHomeButton.js

Aakash, please also add a comment when attaching new tests. What about the test from Tracy which already covers this part?

Comment 38

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testBackandForward.js

Comment 39

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testGoogleSuggestedTerms.js (checked-in)

Comment 40

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testStopandReload.js (checked-in)

Comment 41

[Aakash Desai [:aakashd]]

Attachment: AakashDesai_General_testHomeButton.js

Comment 42

[Aakash Desai [:aakashd]]

All uploaded testscripts have been updated after henrik's in-house review

Comment 43

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

Comment on attachment 375405 [details]
AakashDesai_General_testBackandForward.js

>  var websites=['http://www.google.com/webhp?hl=en&complete=1', 'http://www.yahoo.com/', 'http://www.ask.com/'];
>  var pageElements=['guser', 'searchsubmit', 'q'];

Ask com and yahoo are bad. Both websites redirect to a local domain. In the former case the element 'q' is even not existent.

>  // Click on the Back button for the number of websites visited
>  for (var i = websites.length - 1; i > 0; i--) {
>  	controller.goBack();
>  	controller.waitForElement(new elementslib.ID(controller.tabs.activeTab, pageElements[i]), timeout);
>  }

This should run from length - 2 until >=0. Even a waitForPageLoad would be fine.

As talked on IRC I will attach a new test.

Comment 44

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

Attachment: Test Back/Forward buttons (checked-in)

I modified a couple of things. This is the patch as checked in:
http://hg.mozilla.org/qa/mozmill-tests/rev/07a3dc69a087

Comment 45

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

Comment on attachment 375406 [details]
AakashDesai_General_testGoogleSuggestedTerms.js (checked-in)

> *  Testcase ID #6047 - Test XMLHttpRequest to provide suggested search 

This is testcase id #6041.

>  // Activate the search bar and input in a search parameter
>  controller.click(new elementslib.Name(controller.tabs.activeTab, "q"));
>  controller.type(new elementslib.Name(controller.tabs.activeTab, "q"), "area");

Click is not necessary. Type alone is enough.

Otherwise fine. I'll update the nits and check the test in.

Comment 46

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

Comment on attachment 375406 [details]
AakashDesai_General_testGoogleSuggestedTerms.js (checked-in)

http://hg.mozilla.org/qa/mozmill-tests/rev/ab5804e0e0bd

Comment 47

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

Comment on attachment 375407 [details]
AakashDesai_General_testStopandReload.js (checked-in)

>  controller.click(new elementslib.ID(controller.window.document, "stop-button"));
>  
>  // Reload the NYPost front page and wait for it to completely load
>  controller.refresh();
>  controller.waitForElement(new elementslib.ID(controller.tabs.activeTab, "clssearch"), 6000, 3000);

After hitting stop we should check if the element does NOT exist. In this case clssearch is bad because it's located at the top of the page. Lets take a link from the bottom. Further I have used the delayedAsserNode function to check for the existence after reload. I will move this function to the utilsAPI right now.

Patch with corrections has been checked-in:
http://hg.mozilla.org/qa/mozmill-tests/rev/919453c17559

Comment 48

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

Comment on attachment 375408 [details]
AakashDesai_General_testHomeButton.js

Aakash, please update the test so you check for the loaded page. We have to make sure that it is the correct one. It's still missing when comparing to the Litmus testcase.

Comment 49

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

(In reply to comment #48)
> (From update of attachment 375408 [details])
> Aakash, please update the test so you check for the loaded page. We have to
> make sure that it is the correct one. It's still missing when comparing to the
> Litmus testcase.

I would really like to see that we combine those both tests:
https://litmus.mozilla.org/show_test.cgi?id=5921
https://litmus.mozilla.org/show_test.cgi?id=5989

Using the first one we cover everything from the latter testcase and is indeed a more deeper test.

Comment 50

[Aakash Desai [:aakashd]]

I'm in the process of creating a testscript 5921, I'll add the reference to 5989 to that testscript.

Comment 51

[Aakash Desai [:aakashd]]

Ok,


bug created for a testscript on litmus test cases 5989 and 5921

https://bugzilla.mozilla.org/show_bug.cgi?id=491952

Comment 52

[Merike Sell (:merike)]

Attachment: Litmus 2347 - Create All Day Event

Not including tooltip check as it is impossible to get path with inspector (it is never under cursor) and I wasn't able to figure out from source where it is attached to.

Comment 53

[cmtalbert]

Comment on attachment 379328 [details]
Litmus 2347 - Create All Day Event

I like the approach you are taking here.  But I don't see where you are creating the event that you are verifying the existence of.  It appears that all the event creation code is commented out.  So, we need to create the event before we start trying to verify that it is still there.

Comment 54

[Merike Sell (:merike)]

Attachment: Litmus 2347 - Create All Day Event v2

Doh, this was wrong version. It shouldn't have had tooltip part. Any addtional suggestions?

Comment 55

[cmtalbert]

Comment on attachment 380215 [details]
 Litmus 2347 - Create All Day Event v2

r=ctalbert, this looks great Merike.

Comment 56

[Aakash Desai [:aakashd]]

Are all the testscripts associated with this bug checked-in to hg?

Comment 57

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

Mmh, it's easy to keep lost on this bug. Too many attachments. But as what I see the Download Manager test from Joel is still open. Joel, are you planning to finish it?

Comment 58

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

I will call it fixed. The download test started by Joel hasn't been finished yet and should be moved to its own bug if you decide to continue the test.

Comment 59

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

(In reply to comment #58)
> I will call it fixed. The download test started by Joel hasn't been finished
> yet and should be moved to its own bug if you decide to continue the test.

The Download Manager test is bug 518369 now.

Comment 60

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

Mass move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.