Published using Google Docs
Moblab New-UI Instructions
Updated automatically every 5 minutes

Moblab New-UI Instructions

Configure Moblab

Configuring Boto secrets and Bucket

Installing Moblab updates

Setting DUT wifi

Configuring DUT’s on Moblab

Using Moblab

Running a test suite

Running ‘other’ test suites

Viewing test suite jobs

Aborting jobs

Suite-specific Notes

[CTS/GTS] Filtering modules

Other Actions

Accessing the old UI

Feedback submission

Clearing browser cache

Before starting this section, you should have:

Configure Moblab

  1. Configuring Boto secrets and Bucket

STEP 1 - Open browser, enter localhost/ or the IP of your Moblab and navigate to the ‘Configuration’ page from the navigation sidebar.

STEP 2 Enter the boto key ID, secret and GCS bucket name ( format: gs://[YOUR_BUCKET_URL]/ ) provided by Google in the ‘Configuration Information’ form. When done, press ‘Submit Changes’ and wait for confirmation of submission.

( Note that enabling ‘Moblab cloud integration’ is necessary to edit boto and GCS bucket information. Almost all partners use cloud-integrated Moblabs. Cloud integration is necessary to upload test results to CPCon )

STEP 3 - Refresh the configuration page to confirm that information has been successfully committed.

  1. Installing Moblab updates

STEP 1 - At the top of the configuration page, there is an ‘Update’ button along with an indication of whether there is an update or not.

STEP 2 - Press ‘Ok’ on the confirmation dialog to start update. This should not be done when tests are running.

STEP 3 - Wait for the dialog pop-up that indicates that the update is finished.

  1. Setting DUT wifi

STEP 1 - If needed for your test suite, you can configure wifi information for DUT’s in the form in the bottom of the ‘Configuration’ page.  

Configuring DUT’s on Moblab

STEP 1 - Open browser, enter localhost/ or the IP of your Moblab and navigate to the ‘Manage DUT’s’ page from the navigation sidebar.

STEP 2 - In the ‘Enrollment’ tab of the ‘Manage DUT’s’ page, you may select from the table of DUT’s and click ‘Enroll Selected’ to enroll DUT’s for tests.

(Always check IP address to ensure you're adding right DUT)

STEP 3 - Note that the status of the selected DUT changes to from ‘Not Enrolled’ after enrollment.

STEP 4 (optional) - If you need to add labels, pools, or attributes to any DUT’s navigate to the ‘Attributes/Labels’ tab and use the Add/Remove forms at the head of the page to configure and remove attributes from DUTs.

Using Moblab

Running a test suite

STEP 1 - Open browser, enter localhost/ or the IP of your Moblab and navigate to the ‘Run Suite’ page from the navigation sidebar.

STEP 2 - Select the type of suite that you are trying to run on the tab header.

STEP 3 - Select the model, build target, milestone, and build from the selection dropdowns. Items need to be selected in sequence.

*Note that if there is only one option for any item (e.g., if you only have one model type connected to your Moblab )

STEP 4 - Note that some test suites have special forms to fill out. ( e.g., the modules filter form for CTS/GTS suites.

STEP 5 [Optional] - Select pool if you have multiple DUT pools to manage which DUT’s to run suites on.

STEP 6 - Once all required selections are made, the ‘Run Suite’ button will become clickable.

STEP 7 - After pressing the run suite button, wait for the test suite to start. Once the suite has begun, the page will automatically redirect to the ‘View Jobs’ page.

Running ‘other’ test suites

STEP 1 - The ‘other’ suite allows for users to run suites that are not otherwise lifted. ( e.g., check_setup_storage_qual )

Viewing test suite jobs

STEP 1 - Open browser, enter localhost/ or the IP of your Moblab and navigate to the ‘View Jobs’ page from the navigation sidebar.

STEP 2 - From the ‘View Jobs’ page, you can page through jobs that are queued, running or finished on the Moblab. The header bar can be used to filter by certain parameters.

STEP 3 - Refresh jobs by using the refresh button.

STEP 4 - Any job can be clicked-on for a detail view, which includes information about associated, child jobs.

Aborting jobs

STEP 1 - On the view jobs page, users can abort queued or running jobs by using the ‘Actions’ toolbar ( highlighted ). Jobs to abort can be selected by the left-hand selector.

STEP 1 (cont.) - Note that users can make selection of jobs easier by using the filter options at the top of the page, and selection ‘all’ or ‘visible’ jobs using the table-header selector.

Suite-specific Notes

[CTS/GTS] Filtering modules

STEP 1 - If you need to re-run CTS or GTS suites but only need to run certain tests, you can use the form highlighted on the right to list the specific modules that you want to run ( multiple modules can be included, comma-separated ).

Other Actions

Accessing the old UI

The old, Autotest UI can be accessed via the ‘Old UI’ link in the upper-right corner.

Feedback submission

STEP 1 - In the upper-right corner there is a feedback widget that allows the user to write feedback and associate highlighted screenshots.

STEP 2 - Fill in a contact email ( for further correspondence ) and a description of the problem.

STEP 3 - The user can modify the included screenshot by clicking the ‘Click to highlight or hide info’ portion of the above dialog. This brings up a toolbar tray which allows the user to highlight specific components ( using the yellow icon ) or hide certain fields ( using the black icon ).

STEP 4 - After pressing SEND on the feedback dialog, the user will see a confirmation of the feedback submission.

Clearing browser cache

Navigate to the browsing data dialog in your Chrome browser.

<Google Chrome Instructions>

Select clear cached images and files options in dialog, clear for ‘All Time’