summaryrefslogtreecommitdiffstats
path: root/toolkit/mozapps/update/tests/unit_base_updater/invalidArgInstallDirPathTooLongFailure.js
diff options
context:
space:
mode:
Diffstat (limited to 'toolkit/mozapps/update/tests/unit_base_updater/invalidArgInstallDirPathTooLongFailure.js')
-rw-r--r--toolkit/mozapps/update/tests/unit_base_updater/invalidArgInstallDirPathTooLongFailure.js53
1 files changed, 53 insertions, 0 deletions
diff --git a/toolkit/mozapps/update/tests/unit_base_updater/invalidArgInstallDirPathTooLongFailure.js b/toolkit/mozapps/update/tests/unit_base_updater/invalidArgInstallDirPathTooLongFailure.js
new file mode 100644
index 0000000000..c2746e2bd1
--- /dev/null
+++ b/toolkit/mozapps/update/tests/unit_base_updater/invalidArgInstallDirPathTooLongFailure.js
@@ -0,0 +1,53 @@
+/* This Source Code Form is subject to the terms of the Mozilla Public
+ * License, v. 2.0. If a copy of the MPL was not distributed with this
+ * file, You can obtain one at http://mozilla.org/MPL/2.0/.
+ */
+
+/* Too long install directory path failure test */
+
+async function run_test() {
+ if (!setupTestCommon()) {
+ return;
+ }
+ const STATE_AFTER_RUNUPDATE = gIsServiceTest
+ ? STATE_FAILED_SERVICE_INVALID_INSTALL_DIR_PATH_ERROR
+ : STATE_FAILED_INVALID_INSTALL_DIR_PATH_ERROR;
+ gTestFiles = gTestFilesCompleteSuccess;
+ gTestDirs = gTestDirsCompleteSuccess;
+ setTestFilesAndDirsForFailure();
+ await setupUpdaterTest(FILE_COMPLETE_MAR, false);
+ let path = "123456789";
+ if (AppConstants.platform == "win") {
+ path = "\\" + path;
+ path = path.repeat(30); // 300 characters
+ path = "C:" + path;
+ } else {
+ path = "/" + path;
+ path = path.repeat(1000); // 10000 characters
+ }
+ runUpdate(STATE_AFTER_RUNUPDATE, false, 1, true, null, path, null, null);
+ standardInit();
+ checkPostUpdateRunningFile(false);
+ checkFilesAfterUpdateFailure(getApplyDirFile);
+ await waitForUpdateXMLFiles();
+ if (gIsServiceTest) {
+ // The invalid argument service tests launch the maintenance service
+ // directly so the unelevated updater doesn't handle the invalid argument.
+ // By doing this it is possible to test that the maintenance service
+ // properly handles the invalid argument but since the updater isn't used to
+ // launch the maintenance service the update.status file isn't copied from
+ // the secure log directory to the patch directory and the update manager
+ // won't read the failure from the update.status file.
+ checkUpdateManager(STATE_NONE, false, STATE_PENDING_SVC, 0, 1);
+ } else {
+ checkUpdateManager(
+ STATE_NONE,
+ false,
+ STATE_FAILED,
+ INVALID_INSTALL_DIR_PATH_ERROR,
+ 1
+ );
+ }
+
+ waitForFilesInUse();
+}