{"json_modified": "2016-06-08T09:13:05.311945", "uuid": "e4f8c60a-5949-421b-87b6-5c4de4e3f8b7", "title": "Mozilla automated testing", "url": "/en-US/docs/Mozilla/QA/Automated_testing", "tags": ["Developing Mozilla", "Firefox OS", "Testing", "Automated testing"], "translations": [{"uuid": "b24d4484-2cdf-4d7f-81b6-d029638b61de", "title": "Pruebas automatizadas de Mozilla", "url": "/es/docs/Pruebas_automatizadas_de_Mozilla", "tags": ["Desarrollando_Mozilla", "NecesitaRevisi\u00f3nT\u00e9cnica", "Todas_las_Categor\u00edas", "NecesitaRevisi\u00f3nGramatical", "Pruebas_automatizadas"], "summary": "", "localization_tags": [], "locale": "es", "last_edit": "2010-02-22T17:21:20", "review_tags": []}, {"uuid": "6b1b1bb8-f2fa-4779-a7af-bcc7ddd2ecab", "title": "Mozilla\u306e\u81ea\u52d5\u30c6\u30b9\u30c8", "url": "/ja/docs/Mozilla_automated_testing", "tags": [], "summary": "\u3053\u306e\u30da\u30fc\u30b8\u306f Mozilla \u306e\u958b\u767a\u8005\u304c\u5229\u7528\u3067\u304d\u308b\u81ea\u52d5\u30c6\u30b9\u30c8\u306e\u305f\u3081\u306e\u9078\u629e\u80a2\u306e\u6982\u8981\u3092\u63d0\u4f9b\u3057\u307e\u3059\u3002", "localization_tags": [], "locale": "ja", "last_edit": "2011-01-13T17:00:27", "review_tags": []}, {"uuid": "8e41e6aa-62ea-456d-b254-63d44772c023", "title": "\u57fa\u4e8eMozilla\u7684\u81ea\u52a8\u5316\u6d4b\u8bd5", "url": "/zh-CN/docs/Mozilla_automated_testing", "tags": [], "summary": "You've just written a feature and (hopefully!) want to test it. Or you've decided that an existing feature doesn't have enough tests and want to contribute some. But where do you start? You've looked around and found references to things like \"xpcshell\" or \"mozmill\" or \"talos\". What do they all do? What's the overlap? In short, where should your new tests go?", "localization_tags": [], "locale": "zh-CN", "last_edit": "2012-04-13T01:15:55", "review_tags": []}], "modified": "2016-06-08T09:13:04", "label": "Mozilla automated testing", "localization_tags": [], "locale": "en-US", "id": 203, "last_edit": "2016-06-08T09:13:01", "summary": "These tests are found within the mozilla-central tree, along with the product code. They are all run when a changeset is pushed to mozilla-central, mozilla-inbound, or try, with the results showing up on Treeherder. They can also be run on their own.", "sections": [{"id": "In_production", "title": "In production"}, {"id": "Functional_testing", "title": "Functional testing"}, {"id": "Table_key", "title": null}, {"id": "Performance_testing", "title": null}, {"id": "So_which_should_I_use", "title": "So which should I use?"}, {"id": "Is_it_low-level_code", "title": "Is it low-level code?"}, {"id": "Does_it_cause_a_crash", "title": "Does it cause a crash?"}, {"id": "Is_it_a_layoutgraphics_feature", "title": "Is it a layout/graphics feature?"}, {"id": "Do_you_need_to_verify_performance", "title": "Do you need to verify performance?"}, {"id": "Are_you_testing_UI_features", "title": "Are you testing UI features?"}, {"id": "Are_you_testing_MobileAndroid", "title": "Are you testing Mobile/Android?"}, {"id": "Are_you_doing_none_of_the_above", "title": "Are you doing none of the above?"}, {"id": "Need_to_get_more_data_out_of_your_tests", "title": "Need to get more data out of your tests?"}, {"id": "Need_to_set_preferences_for_test-suites", "title": "Need to set preferences for test-suites?"}], "slug": "Mozilla/QA/Automated_testing", "review_tags": []}