Thursday, 12 May 2011

Tester's Arsenal

or a lot of people, especially those in the management, falsely believes that software testing is easy and that anyone with reasonable intelligence should be able to do it, so much so that they think you can get anyone off the street and if you can put them in front of a computer they should be able to test the software or the application.

This statement is only slightly true because for one type of testing, such as Usability Testing, you can get anyone into a room, sit him/her down in front of a PC and ask to use a piece of software. But this type of testing is not likely to find any bugs, if that was your intention. What you may get out of this exercise is list of usability issues that the so-called 'tester' may come up with, but that in itself is a bit of a hit-and-miss affair. But nevertheless, that's the kind of impression that some people have about what testers do.

However, in reality the skills that a tester needs are wide and varied. There's a saying in the West which goes, 'Jack of all trades and master of none' and a good tester is one who is Jack of all trades, but a really, really good tester is Master of all trades. The thing is, it is relatively easy to be master of one thing but it's much, much harder to be at least competent at many things, and that's precisely what the testers are expected to be; to be sufficiently competent at many things, and that's why I finding being a software tester a great challenge and likewise very rewarding.

The following is a list of tasks that you will be expected to perform, as part of the duty of a tester.
  • Developing test cases
  • Running test cases
  • Capturing trace logs
  • Reporting of defects to the developers
  • Automating repetitive manual tasks
  • Being able to find your way around the filing system of various operating systems, such as Windows, Unix and Linux
  • Being able to find the test data and test results in Oracel or SQL Server databases using nothing but your skill in SQL commands
  • Being able to write batch files in DOS and shell scripts in Unix/Linux
  • Being able to log in remotely from your PC to Test and Database servers to perform your tests or to collect data
  • Uploading files from one server to another, using FTP, SSH, etc.
  • Managing test environment, including setting up and configuring databases.
and a list of systems and tools that I have personally used during my professional life and the level of knowledge required in each of them.

In other words, you need to have skills that Business Analysts have in order to read and understand requirement documents generated by them, using notations such as Use Cases, Sequence diagrams, Class diagrams, State diagrams, Activity diagrams, etc.

Plus, you need to have some of the skills that Developers have in order to read and understand the code they've written, so you can review their Unit Tests and being able to query the implementation of a particular feature in the code.

Furthermore, you need to have skills of a DBA in order to configure and set up the necessary databases and tables in the databases, as well as to be able to backup and restore databases as and when necessary, as part of your testing.

That's not all. You need to have understanding of how a user might end up using the system in order that you can check and test the software from the users' perspective.

With the advent of Agile and Scrum development practices in recent years, there's now a requirement for testers to have skills in test automation, and inevitably that means knowing how to write automated tests in scripting languages such as QTP Visual Basic, Selenium, Java, Python, Ruby, Watir, Cucumber, etc.

In fact, there's never been a time when the demand on the testers have been greater than in the current climate, due to economic pressures to reduce cost and at the same time shorten the development time and to deliver applications, products and services to the market as fast as possible, without sacrificing on the overall software quality.

This means, you better arm yourself to the teeth with business, testing and development skill just to be able to do your job.

    Friday, 6 May 2011

    Jumblogy of Testing

    When I started testing all those years ago, testing was very straight forward. Everyone followed the ONLY way of developing software, i.e. V-Model and consequently, the testing that one has to do was also very simple. All in all, there were only 4 types of testing, namely, Unit Testing, Integration Testing, System Testing and User Acceptance Testing.

    Now, however, the story is very different. There are now so many types of testing, methods and scenarios that have sprouted over the recent years that I decided to record into a type of mind-map.