App store submission testing in Testing Fundamentals - Build an Automation Script

Verify app submission process to app store

Preconditions (3)

Step 1: Navigate to the app submission page in the developer portal

Step 2: Upload the app build file

Step 3: Fill in required metadata fields: app name, description, category, keywords

Step 4: Upload app screenshots for different device sizes

Step 5: Set pricing and availability options

Step 6: Submit the app for review

✅ Expected Result: App submission is accepted and confirmation message is displayed with submission ID

Automation Requirements - Selenium with Python

Assertions Needed:

Verify the app submission page loads correctly

Verify the app build file upload is successful

Verify all required metadata fields are filled and accepted

Verify screenshots upload is successful

Verify pricing and availability options are set

Verify submission confirmation message and submission ID are displayed

Best Practices:

Use explicit waits to handle page loading and element visibility

Use Page Object Model to organize page interactions

Use clear and maintainable locators (id, name, or accessible attributes)

Handle file upload dialogs properly

Include meaningful assertions for each step

Automated Solution

Testing Fundamentals

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
import unittest

class AppStoreSubmissionPage:
    def __init__(self, driver):
        self.driver = driver
        self.wait = WebDriverWait(driver, 10)

    def load(self):
        self.driver.get('https://developer.appstore.com/submission')
        self.wait.until(EC.visibility_of_element_located((By.ID, 'submission-form')))

    def upload_build(self, file_path):
        upload_input = self.wait.until(EC.presence_of_element_located((By.ID, 'build-upload')))
        upload_input.send_keys(file_path)

    def fill_metadata(self, name, description, category, keywords):
        self.driver.find_element(By.ID, 'app-name').clear()
        self.driver.find_element(By.ID, 'app-name').send_keys(name)
        self.driver.find_element(By.ID, 'app-description').clear()
        self.driver.find_element(By.ID, 'app-description').send_keys(description)
        self.driver.find_element(By.ID, 'app-category').send_keys(category)
        self.driver.find_element(By.ID, 'app-keywords').send_keys(keywords)

    def upload_screenshots(self, screenshot_paths):
        for idx, path in enumerate(screenshot_paths, start=1):
            screenshot_input = self.driver.find_element(By.ID, f'screenshot-upload-{idx}')
            screenshot_input.send_keys(path)

    def set_pricing_and_availability(self, pricing_option, availability_option):
        pricing_select = self.driver.find_element(By.ID, 'pricing')
        pricing_select.send_keys(pricing_option)
        availability_select = self.driver.find_element(By.ID, 'availability')
        availability_select.send_keys(availability_option)

    def submit(self):
        submit_button = self.driver.find_element(By.ID, 'submit-button')
        submit_button.click()

    def get_confirmation_message(self):
        message = self.wait.until(EC.visibility_of_element_located((By.ID, 'confirmation-message')))
        return message.text

    def get_submission_id(self):
        submission_id = self.wait.until(EC.visibility_of_element_located((By.ID, 'submission-id')))
        return submission_id.text

class TestAppStoreSubmission(unittest.TestCase):
    def setUp(self):
        self.driver = webdriver.Chrome()
        self.page = AppStoreSubmissionPage(self.driver)

    def test_app_submission(self):
        self.page.load()
        self.assertTrue(self.driver.current_url.endswith('/submission'))

        self.page.upload_build('/path/to/app_build.ipa')

        self.page.fill_metadata(
            name='My Test App',
            description='This is a test app for automation.',
            category='Utilities',
            keywords='test,automation,app'
        )

        self.page.upload_screenshots([
            '/path/to/screenshot1.png',
            '/path/to/screenshot2.png'
        ])

        self.page.set_pricing_and_availability('Free', 'Worldwide')

        self.page.submit()

        confirmation = self.page.get_confirmation_message()
        submission_id = self.page.get_submission_id()

        self.assertIn('submission accepted', confirmation.lower())
        self.assertTrue(len(submission_id) > 0)

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

This script uses Selenium with Python to automate the app store submission process.

The AppStoreSubmissionPage class follows the Page Object Model pattern to keep page interactions organized and reusable.

Explicit waits ensure elements are present or visible before interacting, avoiding timing issues.

Each step from loading the page, uploading files, filling metadata, setting options, and submitting is automated with clear methods.

Assertions check that the page loaded correctly, the confirmation message appears, and a submission ID is shown, verifying success.

The test class TestAppStoreSubmission sets up the browser, runs the test, and cleans up properly.

Common Mistakes - 4 Pitfalls

Using hardcoded sleep delays instead of explicit waits

Using brittle XPath locators that break easily

Not verifying that file uploads succeeded before continuing

Mixing page interaction code directly in test methods

Bonus Challenge

Now add data-driven testing with 3 different app metadata sets to submit multiple apps automatically.

Show Hint

Practice

1. What is the main purpose of app store submission testing?

easy

A. To ensure the app works correctly and meets store rules

B. To write the app's source code

C. To design the app's user interface

D. To create marketing materials for the app

Solution

1. Step 1: Understand app store submission testing

   This testing checks if the app functions well and follows the app store's guidelines.

2. Step 2: Differentiate from other app tasks

   Writing code, designing UI, and marketing are separate tasks not related to submission testing.

3. Final Answer:

   To ensure the app works correctly and meets store rules -> Option A

4. Quick Check:

   Submission testing = check app works and follows rules [OK]

Hint: Submission testing checks app function and rules compliance [OK]

Common Mistakes:

• Confusing testing with coding or design
• Thinking marketing is part of submission testing
• Ignoring app store rules during testing

2. Which of the following is the correct way to test an iOS app before submission?

easy

A. Use TestFlight to distribute the app to testers

B. Upload the app directly to the App Store without testing

C. Test only on the iOS Simulator without real devices

D. Skip testing and rely on user reviews after release

Solution

1. Step 1: Identify iOS testing tools

   TestFlight is Apple's official tool to distribute pre-release apps to testers.

2. Step 2: Evaluate other options

   Uploading without testing or skipping testing risks app failure; simulator-only testing misses real device issues.

3. Final Answer:

   Use TestFlight to distribute the app to testers -> Option A

4. Quick Check:

   iOS pre-release testing = TestFlight [OK]

Hint: Use TestFlight for iOS pre-release testing [OK]

Common Mistakes:

• Skipping real device testing
• Uploading without testing
• Relying only on simulator tests

3. Consider this Android app testing code snippet using Google Play testing tracks:

val testTrack = "internal"
val appVersion = 5
if (appVersion >= 5) {
  println("App ready for $testTrack track testing")
} else {
  println("App version too low for $testTrack track")
}

What will be printed when this code runs?

medium

A. App version too low for internal track

B. App ready for alpha track testing

C. App ready for internal track testing

D. Compilation error due to syntax

Solution

1. Step 1: Check the appVersion value

   appVersion is 5, which is equal to the condition threshold (>= 5).

2. Step 2: Evaluate the if condition

   Since 5 >= 5 is true, the first println runs, printing "App ready for internal track testing".

3. Final Answer:

   App ready for internal track testing -> Option C

4. Quick Check:

   appVersion 5 meets condition, prints ready message [OK]

Hint: Check if condition true to find printed message [OK]

Common Mistakes:

• Misreading the >= operator
• Confusing track names
• Assuming syntax error without checking code

4. You wrote this snippet to test app submission readiness:

if (appInfo.isComplete = true) {
  println("Ready to submit")
} else {
  println("Incomplete app info")
}

What is the error in this code?

medium

A. No error; code runs correctly

B. Missing semicolon at the end of println statements

C. Incorrect method name; should be isCompleteInfo()

D. Using assignment (=) instead of comparison (==) in the if condition

Solution

1. Step 1: Identify the if condition syntax

   The condition uses single = which assigns true instead of comparing.

2. Step 2: Understand correct comparison

   To check equality, use == instead of = in conditions.

3. Final Answer:

   Using assignment (=) instead of comparison (==) in the if condition -> Option D

4. Quick Check:

   Use == for comparison, not = [OK]

Hint: Use == for comparison in if conditions [OK]

Common Mistakes:

• Confusing = and == in conditions
• Assuming semicolons are mandatory in Kotlin/Swift
• Thinking method name is wrong without context

5. You want to test your app on multiple devices before submission. Which approach best ensures thorough testing and smooth app store approval?

hard

A. Rely solely on automated tests without manual device testing

B. Use real devices with different OS versions and TestFlight or Google Play testing tracks

C. Test only on the newest device model and skip beta testing

D. Submit the app immediately and fix issues after release

Solution

1. Step 1: Identify best testing practices

   Testing on real devices with various OS versions catches more issues and matches real user environments.

2. Step 2: Use platform beta testing tools

   TestFlight (iOS) and Google Play testing tracks allow controlled distribution and feedback before public release.

3. Final Answer:

   Use real devices with different OS versions and TestFlight or Google Play testing tracks -> Option B

4. Quick Check:

   Real devices + beta tracks = thorough testing [OK]

Hint: Combine real devices and beta tracks for best testing [OK]

Common Mistakes:

• Testing only on newest device misses compatibility issues
• Skipping manual testing reduces issue detection
• Ignoring beta testing risks app rejection