managing app testing device clouds issues and
play

Managing App Testing Device Clouds: Issues and Opportunities Mattia - PowerPoint PPT Presentation

Managing App Testing Device Clouds: Issues and Opportunities Mattia Fazzini Alessandro Orso Problem Description Study Methodology Android Mobile App Testing Devices and Tests Considered AWS Compatibility Device Farm Android Version


  1. Managing App Testing Device Clouds: Issues and Opportunities Mattia Fazzini Alessandro Orso Problem Description Study Methodology Android Mobile App Testing Devices and Tests Considered AWS Compatibility Device Farm Android Version #Devices CST ver. #Modules #Tests J ELLY B EAN 4.2 2 50 17268 4.2.2_r1 Test Suite J ELLY B EAN 4.3 5 58 18013 4.5_r2.2-cts K IT K AT 4.4 38 73 24039 cts-4.4_r4 L OLLIPOP 5.0 11 93 33929 cts-5.0_r9 L OLLIPOP 5.1 6 96 34207 cts-5.1_r28 M ARSHMALLOW 6.0 15 114 37613 cts-6.0_r32 N OUGAT 7.0 7 124 43494 cts-7.0_r32 Could Testing Infrastructures N OUGAT 7.1 2 133 43598 cts-7.1_r29 Oreo 8.0 11 195 59459 cts-8.0_r20 AWS Device Farm Firebase Test Lab App Center O REO 8.1 4 210 60383 cts-8.1_r16 P IE 9 9 289 84182 cts-9.0_r9 ‣ We used the Compatibility Test Suite to analyze the behavior of 110 devices on the Device farm. We collected a total of 12 million test executions. Study Results and Analysis Future Work ‣ Create a taxonomy of the failures ‣ Identify per-vendor and per-version failures ‣ We observed 9,778 failures and all devices experienced at least one failure ‣ Investigate automatic generation of ‣ We investigated general issues with the cloud infrastructure compatibility-based tests ‣ 58 tests failed on all devices (27 confirmed by a device farm engineer) ‣ Study light-weight monitoring of cloud-based ‣ We investigated security-related issues test executions ‣ 1,307 security-related test failures (caused by 153 different tests)

  2. Managing App Testing Device Clouds: Issues and Opportunities Mattia Fazzini Alessandro Orso Problem Description Study Methodology Android Mobile App Testing Devices and Tests Considered AWS Compatibility Device Farm Android Version #Devices CST ver. #Modules #Tests J ELLY B EAN 4.2 2 50 17268 4.2.2_r1 Test Suite J ELLY B EAN 4.3 5 58 18013 4.5_r2.2-cts K IT K AT 4.4 38 73 24039 cts-4.4_r4 L OLLIPOP 5.0 11 93 33929 cts-5.0_r9 L OLLIPOP 5.1 6 96 34207 cts-5.1_r28 M ARSHMALLOW 6.0 15 114 37613 cts-6.0_r32 N OUGAT 7.0 7 124 43494 cts-7.0_r32 Could Testing Infrastructures N OUGAT 7.1 2 133 43598 cts-7.1_r29 Oreo 8.0 11 195 59459 cts-8.0_r20 AWS Device Farm Firebase Test Lab App Center O REO 8.1 4 210 60383 cts-8.1_r16 P IE 9 9 289 84182 cts-9.0_r9 ‣ We used the Compatibility Test Suite to analyze the behavior of 110 devices on the Device farm. We collected a total of 12 million test executions. Study Results and Analysis Future Work ‣ Create a taxonomy of the failures ‣ Identify per-vendor and per-version failures ‣ We observed 9,778 failures and all devices experienced at least one failure ‣ Investigate automatic generation of ‣ We investigated general issues with the cloud infrastructure compatibility-based tests ‣ 58 tests failed on all devices (27 confirmed by a device farm engineer) ‣ Study light-weight monitoring of cloud-based ‣ We investigated security-related issues test executions ‣ 1,307 security-related test failures (caused by 153 different tests)

  3. Managing App Testing Device Clouds: Issues and Opportunities Mattia Fazzini Alessandro Orso Problem Description Study Methodology Android Mobile App Testing Devices and Tests Considered AWS Compatibility Device Farm Android Version #Devices CST ver. #Modules #Tests J ELLY B EAN 4.2 2 50 17268 4.2.2_r1 Test Suite J ELLY B EAN 4.3 5 58 18013 4.5_r2.2-cts K IT K AT 4.4 38 73 24039 cts-4.4_r4 L OLLIPOP 5.0 11 93 33929 cts-5.0_r9 L OLLIPOP 5.1 6 96 34207 cts-5.1_r28 M ARSHMALLOW 6.0 15 114 37613 cts-6.0_r32 N OUGAT 7.0 7 124 43494 cts-7.0_r32 Could Testing Infrastructures N OUGAT 7.1 2 133 43598 cts-7.1_r29 Oreo 8.0 11 195 59459 cts-8.0_r20 AWS Device Farm Firebase Test Lab App Center O REO 8.1 4 210 60383 cts-8.1_r16 P IE 9 9 289 84182 cts-9.0_r9 ‣ We used the Compatibility Test Suite to analyze the behavior of 110 devices on the Device farm. We collected a total of 12 million test executions. Study Results and Analysis Future Work ‣ Create a taxonomy of the failures ‣ Identify per-vendor and per-version failures ‣ We observed 9,778 failures and all devices experienced at least one failure ‣ Investigate automatic generation of ‣ We investigated general issues with the cloud infrastructure compatibility-based tests ‣ 58 tests failed on all devices (27 confirmed by device farm engineers) ‣ Study light-weight monitoring of cloud-based ‣ We investigated security-related issues test executions ‣ 1,307 security-related test failures (caused by 153 different tests)

  4. Managing App Testing Device Clouds: Issues and Opportunities Mattia Fazzini Alessandro Orso Problem Description Study Methodology Android Mobile App Testing Devices and Tests Considered AWS Compatibility Device Farm Android Version #Devices CST ver. #Modules #Tests J ELLY B EAN 4.2 2 50 17268 4.2.2_r1 Test Suite J ELLY B EAN 4.3 5 58 18013 4.5_r2.2-cts K IT K AT 4.4 38 73 24039 cts-4.4_r4 L OLLIPOP 5.0 11 93 33929 cts-5.0_r9 L OLLIPOP 5.1 6 96 34207 cts-5.1_r28 M ARSHMALLOW 6.0 15 114 37613 cts-6.0_r32 N OUGAT 7.0 7 124 43494 cts-7.0_r32 Could Testing Infrastructures N OUGAT 7.1 2 133 43598 cts-7.1_r29 Oreo 8.0 11 195 59459 cts-8.0_r20 AWS Device Farm Firebase Test Lab App Center O REO 8.1 4 210 60383 cts-8.1_r16 P IE 9 9 289 84182 cts-9.0_r9 ‣ We used the Compatibility Test Suite to analyze the behavior of 110 devices on the Device farm. We collected a total of 12 million test executions. Study Results and Analysis Future Work ‣ Create a taxonomy of the failures ‣ Identify per-vendor and per-version failures ‣ We observed 9,778 failures and all devices experienced at least one failure ‣ Investigate automatic generation of ‣ We investigated general issues with the cloud infrastructure compatibility-based tests ‣ 58 tests failed on all devices (27 confirmed by a device farm engineer) ‣ Study light-weight monitoring of cloud-based ‣ We investigated security-related issues test executions ‣ 1,307 security-related test failures (caused by 153 different tests)

  5. Managing App Testing Device Clouds: Issues and Opportunities Mattia Fazzini Alessandro Orso Problem Description Study Methodology Android Mobile App Testing Devices and Tests Considered AWS Compatibility Device Farm Android Version #Devices CST ver. #Modules #Tests J ELLY B EAN 4.2 2 50 17268 4.2.2_r1 Test Suite J ELLY B EAN 4.3 5 58 18013 4.5_r2.2-cts K IT K AT 4.4 38 73 24039 cts-4.4_r4 L OLLIPOP 5.0 11 93 33929 cts-5.0_r9 L OLLIPOP 5.1 6 96 34207 cts-5.1_r28 M ARSHMALLOW 6.0 15 114 37613 cts-6.0_r32 N OUGAT 7.0 7 124 43494 cts-7.0_r32 Could Testing Infrastructures N OUGAT 7.1 2 133 43598 cts-7.1_r29 Oreo 8.0 11 195 59459 cts-8.0_r20 AWS Device Farm Firebase Test Lab App Center O REO 8.1 4 210 60383 cts-8.1_r16 P IE 9 9 289 84182 cts-9.0_r9 ‣ We used the Compatibility Test Suite to analyze the behavior of 110 devices on the Device farm. We collected a total of 12 million test executions. Study Results and Analysis Future Work ‣ Create a taxonomy of the failures ‣ Identify per-vendor and per-version failures ‣ We observed 9,778 failures and all devices experienced at least one failure ‣ Investigate automatic generation of ‣ We investigated general issues with the cloud infrastructure compatibility-based tests ‣ 58 tests failed on all devices (27 confirmed by a device farm engineer) ‣ Study light-weight monitoring of cloud-based ‣ We investigated security-related issues test executions ‣ 1,307 security-related test failures (caused by 153 different tests)

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend