How to Test Order Tracking on Android (Complete Guide)

Order tracking is a critical feature in e-commerce Android apps, allowing users to monitor the status of their orders. However, common failures in this feature can lead to frustrated users, negative r

Why Order Tracking Testing Matters

Order tracking is a critical feature in e-commerce Android apps, allowing users to monitor the status of their orders. However, common failures in this feature can lead to frustrated users, negative reviews, and ultimately, lost business. Some common issues include:

• Inaccurate or outdated order status information
• Failure to update order status in real-time
• Inability to track orders due to technical issues or poor user interface design
• Inaccessibility of order tracking feature for users with disabilities

These issues can have a significant impact on user experience and satisfaction. For example, a user who is unable to track their order may contact customer support, leading to increased support costs and decreased user satisfaction.

What to Test

To ensure that the order tracking feature works correctly, the following test cases should be considered:

• Happy path scenarios:

+ Successful order placement and tracking

+ Order status updates in real-time

+ Ability to cancel or modify orders

• Error scenarios:

+ Invalid or missing order information

+ Network errors or connectivity issues

+ Server-side errors or timeouts

• Edge cases:

+ Orders with multiple items or complex shipping arrangements

+ Orders with special instructions or handling requirements

+ Orders that are cancelled or refunded

• Accessibility considerations:

+ Screen reader compatibility for visually impaired users

+ High contrast mode compatibility for users with visual sensitivities

+ Ability to navigate order tracking feature using accessibility tools (e.g. switch access)

Some specific test cases for order tracking on Android apps include:

1. Test case 1: Place an order and verify that the order status is updated correctly.
2. Test case 2: Cancel an order and verify that the order status is updated correctly.
3. Test case 3: Modify an order and verify that the order status is updated correctly.
4. Test case 4: Test order tracking with multiple items in the order.
5. Test case 5: Test order tracking with complex shipping arrangements (e.g. multiple shipping addresses).
6. Test case 6: Test order tracking with special instructions or handling requirements.
7. Test case 7: Test order tracking with screen reader enabled.
8. Test case 8: Test order tracking in high contrast mode.
9. Test case 9: Test order tracking using switch access.
10. Test case 10: Test order tracking with network errors or connectivity issues.
11. Test case 11: Test order tracking with server-side errors or timeouts.
12. Test case 12: Test order tracking with invalid or missing order information.

Manual Testing Approach

To manually test order tracking on an Android app, follow these steps:

1. Step 1: Install the app on an Android device.
2. Step 2: Place an order using the app.
3. Step 3: Verify that the order status is updated correctly.
4. Step 4: Test each of the test cases listed above.
5. Step 5: Use accessibility tools (e.g. screen reader, high contrast mode) to test accessibility considerations.
6. Step 6: Test order tracking with network errors or connectivity issues (e.g. by disabling Wi-Fi or cellular connectivity).
7. Step 7: Test order tracking with server-side errors or timeouts (e.g. by simulating a server-side error using a tool like Charles Proxy).

Automated Testing Approach

To automate order tracking testing on Android, tools like Appium or Espresso can be used. For example, using Appium, the following code snippet can be used to automate test case 1:

import io.appium.java_client.AppiumDriver;
import io.appium.java_client.MobileElement;
import io.appium.java_client.android.AndroidDriver;

public class OrderTrackingTest {
  public static void main(String[] args) {
    // Set up Appium driver
    AppiumDriver<MobileElement> driver = new AndroidDriver<>(new URL("http://localhost:4723/wd/hub"));

    // Place an order
    driver.findElement(By.id("place_order_button")).click();

    // Verify order status
    String orderStatus = driver.findElement(By.id("order_status_text")).getText();
    Assert.assertEquals("Order placed successfully", orderStatus);
  }
}

Similarly, using Espresso, the following code snippet can be used to automate test case 1:

import androidx.test.espresso.Espresso;
import androidx.test.espresso.assertion.ViewAssertions;
import androidx.test.espresso.matcher.ViewMatchers;

public class OrderTrackingTest {
  @Test
  public void testOrderTracking() {
    // Place an order
    Espresso.onView(ViewMatchers.withId(R.id.place_order_button)).perform(ViewActions.click());

    // Verify order status
    Espresso.onView(ViewMatchers.withId(R.id.order_status_text)).check(ViewAssertions.matches(ViewMatchers.withText("Order placed successfully")));
  }
}

How SUSA Tests Order Tracking Autonomously

SUSA tests order tracking autonomously using a combination of user personas and dynamic testing. The curious persona tests happy path scenarios, such as placing an order and verifying order status. The impatient persona tests error scenarios, such as network errors or server-side errors. The accessibility persona tests accessibility considerations, such as screen reader compatibility and high contrast mode compatibility.

The adversarial persona tests edge cases, such as orders with multiple items or complex shipping arrangements. The novice persona tests basic order tracking functionality, such as placing an order and verifying order status. The student persona tests order tracking with special instructions or handling requirements. The teenager persona tests order tracking with social media sharing or notifications. The business persona tests order tracking with business-related features, such as order tracking for multiple orders or shipments. The power user persona tests advanced order tracking features, such as custom order tracking or order tracking with multiple devices.

SUSA's autonomous testing approach ensures that order tracking is thoroughly tested, including happy path scenarios, error scenarios, edge cases, and accessibility considerations. By using a combination of user personas and dynamic testing, SUSA can identify issues that may not be caught by manual testing or automated testing alone.