Mobile apps just have to work and deliver value or they quickly get deleted. Your reputation as a developer and that of your business often hinge on the experience of the user and ratings on your apps. A good experience and ratings can help your app go viral and business to boom; and your value to the company grows. However, when a user is upset, you want to know. When your app crashes, you need the data.
Hudson and Jenkins have already plenty of plugins to extend their capabilities (notifiers, tags, post build actions, etc...)
But those tools are so versatile, you'll always want to leverage them to address a particular problem in your company environment: knowing how to extend them will come handy sooner than later !
In this talk, the attendee will learn what to expect when creating a Hudson / Jenkins plugin :
Mozilla builds and tests software at tremendous scale, for projects such as Firefox for Desktop and Android, and Firefox OS. A single code "check in" consumes over 200 compute hours to complete builds as well as correctness and performance tests on multiple platforms. We recently ran a record 73,000 test jobs in a single day. This talk will discuss the open source tools we use to optimize and automate the management of the hardware and software required to handle this scale of release engineering activity on our hybrid in-house/AWS infrastructure.
Although we live in a modular world, it will always make sense to write and run integration-tests that allow the testing of the whole application, and not just a module. These integration-tests are often the only way to test real usage scenarios that rely on multiple modules and that can be affected by other modules and by the packaging of your application.
This past year I was asked to evaluate the accessibility of my team's product. At the time, I was not entirely clear what that really meant. I knew there were people out there that used different input/output devices, could not perceive certain colours, had difficulty seeing small print-- and encompassed a variety of other concerns, but I really didn't know how that related to our product, or if our implementation helped or hindered these users (roughly 16% of the population).
After a fair bit of investigation, it is a lot clearer how the things we do in our design and code relates to these accessibility concerns for our users.
Eclipse Jubula is a tool for writing automated GUI tests that can be used as acceptance tests and/or regression tests. Its main aim is to help teams:
Automated testing rocks, don’t get me wrong. But a good test strategy involves knowing when to automate and when to get your hands dirty with some manual testing.
Before you fall asleep – manual testing doesn’t have to mean boring repetition. In fact, manual testing can be exciting, revitalizing and helpful for the project and the software quality. And everyone has to do it at some point or another – so it’s worth working on making it better.