Variables might include appPackageName for Android, or bundle ID for iOS. Depending on the app, maybe use instruments for iOS or adb for Android.
Error recovery steps: if a step fails, take a screenshot or log the error, then proceed to clean up. Also, report results at the end. Maybe include a function to restart the app between test cases if there are multiple scenarios.
So, the mobile script will start with initializing the device, launching the app, perform actions, and then close it. Each step is a test case step, with screenshots perhaps.
function testCreateMatch() { startTest("Match Creation"); testCaseStep("Navigate to Match Screen", "Clicking create match button..."); click(BTN_CREATE_MATCH); waitFor(1); stepEnd("PASSED"); Tbao Hub Blue Lock Rivals Mobile Script
I should outline the script with setup, test steps, and teardown. Use variables for dynamic data. Let's think of a simple test case: login with valid credentials, check profile data, start a session, check if the session is created, then log out. Another test case could be creating a rival, verifying the rival's details.
testCaseStep("Validate Home Screen", "Checking welcome message..."); verifyText(TEXT_WELCOME_MESSAGE, "Welcome Back", "Failed to detect welcome message."); stepEnd("PASSED"); } ID: TCL-002 Objective: Verify match creation functionality.
Include assertions to check if expected elements are present. For example, after logging in, verify the user's name is displayed. If the element ID is 'user_profile_name', read the text and compare with expected. Also, report results at the end
function testInvalidLogin() { startTest("Invalid Login"); waitForElement(TXT_USERNAME, 5); // Ensure login screen is active typeText(TXT_USERNAME, "wronguser"); typeText(TXT_PASSWORD, "wrongpass"); click(BTN_LOGIN);
Wait, the user provided an example before. Let me check that. They had a script with variables, setupDevice, login, testMatchCreation, etc., using functions and methods. So maybe the script should follow a similar structure.
Also, handle different scenarios: what if the app crashes? The script might need to detect that and fail the test. Each step is a test case step, with screenshots perhaps
(Using T-Plan Automation Syntax) Test Script Overview Script Name: BlueLockRivals_MobileTest.tst Purpose: Validate core functionalities of the Blue Lock Rivals mobile app on Android/iOS platforms. Test Devices: Android Emulator (API 30+), iOS Simulator (15.0+) Dependencies: App installed via adb install or Xcode. Requires test user credentials. Variables & Constants // Test Data string APP_ACTIVITY = "com.blue_lock_rivals.MainActivity"; string ANDROID_APP_PACKAGE = "com.blue_lock_rivals"; string IOS_APP_BUNDLE = "com.blueLockRivals.mobile";
I need to make sure the script is modular. Each function should handle a specific task, making it reusable. For example, a function to handle login that can be called at the beginning of multiple test cases.
Need to write the script in the language or syntax that T-Plan uses. Since I'm not 100% sure, maybe use pseudocode with keywords like startTest, endTest, waitForElement, click, typeText, etc. Also, include comments for clarity.