August 2015 - Walty Blog

August 28, 2015Walty 3 Comments

Simple Gmail Notes – Chrome Extension

For a long time, I wanted a browser extension that allows me simply add notes to the Gmail. It is because I need some easy way to mark down the comments on the resumes of candidates, Sometimes they would send the resumes across a long time span. Of course I could mark down the notes on evernote, but it's time-consuming and difficult to have an organized list of comments overall candidates, most of which I would not review for the second time.

There was a useful plugin called Notes-For-Gmail. Yet it stopped functioning months ago, and I have no way to contact the author.

Finally I decided my own one, as I really need this. And it seems to be a good chance to learn the Google chrome extension writing as well.

August 17, 2015Walty No Comments

Testing On Mobile Device – Part 2 – Network Data Mocking

Say, we have a perfect automation system,and we could basically control anything on the device, precisely. Would that imply we are going to have a perfect testing system right away?

Maybe not. Because data is also relevant.

For most automated testing systems, there is a common pattern:

actions / inputs to the system

assertions on the output

further actions

further assertions

...

That's true for testing system for either web based testing system (e.g. selenium), or mobile applications (e.g. iOS automated testing).

If the system can be fully controlled, such as a standalone invoice system, it would be easy. However, for the other system, especially the mobile apps with dynamic data, that would not be the case.

August 14, 2015Walty No Comments

Testing On Mobile Device – Part 1 – Sikuli – VNC

Facts

We are a small sized IT company, with around 50 staff and 30 developers.
Like most other IT companies in the world, we don't have full-time engineers work as QA.
Most engineers got more one project at a time. (One for development and one for maintenance.)
Engineers don't have the time (or they just don't care) to write the unit tests and functional tests, even if the tools are provided by iOS and Android development frameworks.
Our QA did most of the testing manually, but it's a boring task. And they are not capable of writing the codes for the unit tests and functional tests.
The Apps for iOS simulator and device have significantly different architecture, but the apps for Android simulator and device are the same.
If the tasks depend on the work of engineers, it normally means the tasks need cooperation of engineer and QA, and the timing would be a big problem.**

So, our goal is

Allow our QA to set up the automated tests for the mobile applications, with zero or minimum efforts of engineering.