Chris Atherton did the closing keynote of the GOTO Berlin 2015 conference in which she talked about designing software. She suggests that, in stead of relying on professional opinions on how software should look or work, it can be better to go out and get data from real users. InfoQ interviewed her about designing and testing user interfaces.
Convinced that “whatever can be unit tested should be unit tested”, Mona El Mahdy, a Software Engineer in Test at Google, has written a blog post proposing several approaches to perform unit tests on the user interface of Android applications. Mahdy recommends Robolectric and the Android Studio Gradle plug-in for general unit testing, and Espresso or UI Automator for creating and running UI tests.
Google has open sourced Espresso, an Android automated testing framework that enables one to run tests on x86 machines in the cloud in a multi-threaded environment, solving the concurrency issues associated with UI testing.
Clutch enables developers to write hybrid applications for iOS and to run A/B test experiments on iOS and Android devices.
Of all the forms of testing there is one that simply cannot be skipped. It doesn’t matter how good your automated tests are, manual testing still has to be performed before an application ships. With the release of MS Test Manager 2012, Microsoft intends to make it manual tests significantly easier.
Google has decided to open source WindowTester Pro, a Java tool used for automated SWT and Swing GUI testing.
Visual Studio Lab Management 2010 is a highly integrated virtualization, development, and testing tool. When testers encounter an error they can create a snapshot of the virtual environment at that moment: not just a screenshot, but the current state of the application or website and all the servers involved.