A blog writer might wonder how to test a pen. After all, the question is simple – how would you know if the product that you are testing really works? Well, automation is one way of making sure that you get the most out of your testing and R&D department. Automation not only saves time and money, it also makes the testing and development process transparent from the customer’s point of view. How to test a pen is no longer a question in the blogosphere or in a forum. It has become a common topic of conversation for those who are passionate about software and IT.
When I started as a tester, my co-workers and I used to joke that we had to put our heads together and figure out how to test a pen so we wouldn’t get sued by our customers. In fact, we made a rule to never use the same pen on the same platform. Another example of this rule would be to only test mobile devices. One of us was fond of the BlackBerry and would not use it on an Apple device. It made for good sense and we got really good at deciding which test cases or devices we wanted to test, based on our actual use and sensitivity of the devices.
The funny thing is that we never got a really good group of test cases together. Some of us would bring a BlackBerry or an iPhone, but most of us would get a Windows XP PC or Vista PC. Why? Why do testers think like that? How would they test a pen if they actually used it and practiced with it?
The reality is that software testers don’t just test better if they write blog posts about how they test a pen. They need to think like a regular buyer. In other words, the tester needs to understand what makes a consumer purchase a product in the first place. So, the software tester would need to ask himself, “Why am I buying this pen?” Then he would have to imagine all of the reasons why a consumer might buy it.
How To Test A Pen?
How to write good testing blogs isn’t rocket science, but it does require some practice. Testing software requires some understanding of the software as well as the end-user experience. Test users aren’t stupid. As testers, we are expected to demonstrate our ability to deal with certain situations. Sometimes a test tester must demonstrate a lack of knowledge to his peers, in order to justify his or her lack of ability to perform a certain task.
In order to learn how to test a pen properly, a professional must understand the way a particular brand of pen feels in real life. For example, an engineer must test how a pen feels when he writes on it with his actual hands, in a similar way to how a car driver tests the performance of a car’s brakes by driving it across a room. A tester must also consider how the pen is going to feel when it has been soaked in ink. When that happens, he or she should be ready to explain what he or she is seeing and what he or she is testing with the various elements of that test.
There are many software development test cases, which a tester could fill if he or she wanted to. However, a successful candidate for this job is someone who can tell a story about the way they used the specific tool. That story needs to be coherent, detailed and logical. If the blogger cannot make this transition from a developer to a tester then the blog may be a waste of time.
The final post in the series will deal with how to test a pen in the context of a specific function. The Gurock development team has found that their test automation platform lends itself well to blog posts. So far, the platform has been adopted by over one thousand companies around the world. Whether or not this number is growing or decreasing is anyone’s guess, but it’s a trend that is unlikely to abate any time soon.