How To Deliver The Best User Experience
Electric Imp’s BlinkUp™ technology and all BlinkUp Software Development Kit (SDK) features are tested by the Electric Imp Quality Assurance Department. However, the mobile BlinkUp applications you create using Electric Imp’s SDKs also need testing for all your custom development components and features, in addition to testing overall integration with BlinkUp. This guide helps explain the scope of testing for your mobile BlinkUp app, touches on QA best practices, and recommends some test scenarios.
Both your app content and integrations with Electric Imp components need testing throughout the development process. The following sections list testing requirements and categorize them into two main sections: your custom content and Electric Imp BlinkUp integrations.
The Electric Imp Dev Center has more information regarding SDK minimum specifications.
Before BlinkUp flashing begins, users need a way to configure their connectivity settings. It is these settings that will be sent by BlinkUp to the imp-enabled device.
BlinkUp functionality itself is tested and verified by Electric Imp, but your app could potentially interfere with the flashing process, thus causing BlinkUp failures. This is typically the result of app activity causing BlinkUp to drop frames.
After the BlinkUp flashing there is a polling process which repeatedly checks the Electric Imp impCloud™ for information about the imp-enabled device’s registration. Either the device connects to the impCloud and information is successfully retrieved, or the polling will fail after a timeout period.
This identifier differentiates one end-user from another. An end-user’s plan ID is generated when they first configure a production product using BlinkUp. Your app design chooses whether the customer’s plan ID is retained throughout ownership of the product (based on their account in your backend system), or if it is re-generated every time the product needs to be re-configured, for example when the customer changes their local WiFi network details. More information on Plan IDs is available in the Dev Center.
This event-triggered webhook is called when a customer successfully configures a product using BlinkUp. More information on Webhooks is available in the Dev Center.
This action clears network access credentials and enrollment data from an imp-enabled device. You may or may not include this feature in your application. An example use case might be someone re-selling their product and wanting to first clear their product data.
Creating a test plan and testing strategy, in addition to continuously testing throughout the entire development process, are two examples of relatively easy best practices that pay big dividends when ensuring a desired level of product quality within project timelines. The following examples of QA best practices are specifically relevant for mobile testing.
Each application will have its own unique test cases as related to specific individual aspects within the application. These test scenarios provided here are meant to provide an example high-level concept of what to test. In order to provide a bit more context, the format of these test scenarios borrow concepts from user stories and behavior-driven development acceptance criteria. All these test scenarios will have multiple test cases and particular test steps in relation to your application. In addition, a few example generic test-case considerations are also provided at the end.