FAILURE: browsertests-Wikidata-WikidataTests-linux-firefox-sauce Build #593 (Mon, 18 Apr 2016 01:22:00 +0000) |
35 failed, 0 skipped
Failed Tests
Test Name | Duration | Age |
Adding references to statements.Add reference with multiple snaks | 22 sec | 1 |
Authority control gadget test.Check links created by gadget (outline example : | Q12480 | false |) | 27 sec | 46 |
Authority control gadget test.Check links created by gadget (outline example : | Q12480 | true |) | 1 min 3 sec | 46 |
Creating statements.Cancel statement (outline example : | press the ESC key in the claim entity selector input field |) | 40 sec | 24 |
Creating statements of type string.Adding a statement of type string (outline example : | it's a string | press the RETURN key in the claim value input field |) | 27 sec | 1 |
Creating statements of type string.Adding a statement of type string and reload page | 38 sec | 1 |
Edit description.Description with special input (outline example : | "0" | "0" |) | 28 sec | 1 |
Edit sitelinks.Remove multiple sitelinks | 57 sec | 44 |
Edit sitelinks.Save sitelink and reload (outline example : | press the RETURN key in the pagename input field |) | 35 sec | 1 |
Using geo properties in statements.Geo UI should work properly | 37 sec | 4 |
Using geo properties in statements.Geo parser in the preview and precision detection should work properly (outline example : | 1 1 | 1°N, 1°E | ±1° |) | 51 sec | 4 |
Using geo properties in statements.Geo parser in the preview and precision detection should work properly (outline example : | 1 S 1 W | 1°S, 1°W | ±1° |) | 52 sec | 4 |
Using geo properties in statements.Geo parser in the preview and precision detection should work properly (outline example : | 42.1538, 8.5731 | 42°9'13.7"N, 8°34'23.2"E | ±0.0001° |) | 50 sec | 4 |
Using geo properties in statements.Geo parser in the preview and precision detection should work properly (outline example : | 42° 09.231' N 008° 34.386' E | 42°9'13.86"N, 8°34'23.16"E | to 1/100 of an arcsecond |) | 58 sec | 4 |
Using geo properties in statements.Geo parser in the preview and precision detection should work properly (outline example : | 52°29'53"N, 13°22'51"E | 52°29'53"N, 13°22'51"E | to an arcsecond |) | 51 sec | 4 |
Using geo properties in statements.Geo parser in the preview and precision detection should work properly (outline example : | 52°29'N, 13°22'E | 52°29'N, 13°22'E | to an arcminute |) | 1 min 1 sec | 4 |
Using monolingual properties in statements.Adding a statement of type monolingual (outline example : | German |) | 37 sec | 1 |
Using monolingual properties in statements.Adding a statement of type monolingual and use keyboard to select language (outline example : | English |) | 8 sec | 2 |
Using monolingual properties in statements.Adding a statement of type monolingual and use keyboard to select language (outline example : | German |) | 52 sec | 1 |
Using time properties in statements.Time UI should work properly | 38 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 1 1999 | 1 January 1999 | Gregorian | day |) | 46 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 1 | January 1 | Julian | month |) | 45 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 ad | 1 | Julian | year |) | 47 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 b.c. | 1 BCE | Julian | year |) | 50 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 bc | 1 BCE | Julian | year |) | 56 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 ce | 1 | Julian | year |) | 52 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1 | 1 | Julian | year |) | 46 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 10000 | 10000 years CE | Gregorian | 10,000 years |) | 44 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 100000 | 100000 years CE | Gregorian | 100,000 years |) | 45 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1000000 BC | 1 million years BCE | Julian | million years |) | 47 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 10000000 | 10 million years CE | Gregorian | ten million years |) | 47 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 100000000 | 100 million years CE | Gregorian | hundred million years |) | 49 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 1000000000 BCE | 1 billion years BCE | Julian | billion years |) | 48 sec | 4 |
Using time properties in statements.Time parser in the preview and precision detection should work properly (outline example : | 12.11.1981 | 12 November 1981 | Gregorian | day |) | 46 sec | 4 |
Using url properties in statements.Save a statement of type url and check the output (outline example : | http://عربي.امارات/en/ |) | 52 sec | 2 |
All Tests
Package | Duration | Fail | Skip | Total |
(root) | 2 hr 29 min | 35 | 0 | 210 |
_______________________________________________
QA-Alerts mailing list
QA-Alerts@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/qa-alerts
|