Test area for graphical user interface of electronic device software testing

Abstract

1. Name of the product in this design: Test area for graphical user interface of electronic device software testing. 2. Purpose of this design: An electronic device. 3. The key design features of this product are the graphical user interface in the electronic device for which protection is sought. 4. The image or photograph that best illustrates the key design points: Design 1, Change State Diagram 2. 5. Design 1 is designated as the basic design. 6. Purpose of Graphical User Interface: Graphical user interfaces are used for software testing. The graphical user interface requests protection for specific areas used in automated software testing. 7. Human-computer interaction method of graphical user interface: In response to the user touching or clicking the "Automated Test" button in the main view of Design 1, the graphical user interface changes from the main view of Design 1 to the Design 1 change state diagram 1 to display the requirement upload window; in response to the user touching or clicking the "Start Test" button in the Design 1 change state diagram 1 after uploading the requirement, the graphical user interface changes from the Design 1 change state diagram 1 to the Design 1 change state diagram 2 to display the automated testing process; in response to a problem being detected, the graphical user interface changes from the Design 1 change state diagram 2 to the Design 1 change state diagram 3 to display relevant information about the problem. In response to a user's uploaded request, touching or clicking the "Start Test" button in the main view of Design 2 will change the graphical user interface from the main view of Design 2 to Design 2 Change State Figure 1 to show the automated testing process; in response to a detected problem, the graphical user interface will change from Design 2 Change State Figure 1 to Design 2 Change State Figure 2 to show relevant information about the problem. In response to a user's uploaded request, touching or clicking the "Start Test" button in the Design 3 main view will change the graphical user interface from the Design 3 main view to the Design 3 change state diagram to display the automated testing process. In response to a user touching or clicking the "Automated Testing" button in the main view of Design 4, the graphical user interface changes from the main view of Design 4 to Design 4 Change State Figure 1 to display the requirement upload window; in response to a user touching or clicking the "Start Testing" button in Design 4 Change State Figure 1 after uploading requirements, the graphical user interface changes from Design 4 Change State Figure 1 to Design 4 Change State Figure 2 to display the automated testing process; in response to a problem being detected, the graphical user interface changes from Design 4 Change State Figure 2 to Design 4 Change State Figure 3 to display relevant information about the problem. In response to a user's uploaded request, touching or clicking the "Start Test" button in the main view of Design 5 will change the graphical user interface from the main view of Design 5 to Design 5 Change State Figure 1 to show the automated testing process; in response to a detected problem, the graphical user interface will change from Design 5 Change State Figure 1 to Design 5 Change State Figure 2 to show relevant information about the problem. In response to a user's uploaded request, touching or clicking the "Start Test" button in the Design 6 main view will change the graphical user interface from the Design 6 main view to the Design 6 change state diagram to display the automated testing process. 8. Other situations requiring explanation: The portions of the graphical user interface shown by the dashed lines in the views of Design 1 to Design 6 do not constitute the parts protected by this design.

Images