Father’s day, a customary day for the celebration of fatherhood. Ever wondered who started the Software Testing practice? Or who is the pioneer of Software Quality? Who invented the Internet and the World Wide Web? Who wrote the first ever program? Who built the computer? Leave it all, who is the father of computing? On this Father’s day, let’s know about and thank the fathers of technologies shaping our present and the future!
Recently a lot has been written & talked about the future of Manual Testing. Manual Testing is indispensable part of ensuring a high quality software. On the other hand, Automation Tests help you cut down the release cycle time. But usability & human behavior cannot be automated. With reduced time-to-market there is an added pressure on enterprises to seek automation alternatives. With the rise & growth of new technologies, people are more interested in scripting. But Manual Testing is the input to Automation scripts. Unless AI technology matches a human brain, Manual tests are best kept ‘manual’. You cannot automate everything. Cut the crap! Whatever be the debate but still Manual testers are finding it hard to stay relevant in today’s job market. Why?
Quality – Why is this word so important for your software? Software teams today involve a number of people: developers, testers, support engineers, designers, product managers, and executive stake holders. A low quality software impacts all of these or in other words everyone in the team is responsible for the quality of software delivered. When we look into the overall effectiveness or cost manual testing still have a pivotal role to play. Unfortunately, very little discussion is only happening on how to improve efficiency of manual testing instead most of discussions are happening on how to increase the level of automation. Many of us would advocate the fact that Manual Testing is no longer needed, and I know it well why they think so. It is mostly because of the drawbacks and challenges associated with Manual Testing.
Different browsers render applications differently, so web applications need to be able to detect on which browser they are running and adjust their app code accordingly. Successfully testing all browsers and all versions are no small feat which is exactly why Sauce Labs built their solution on Selenium. To enable QA teams to execute Selenium based automation suites on multiple permutations, operating systems, and versions, for multiple browsers and browser versions.
At first glance, this seems like we’re done and this is the perfect solution to achieve complete application matrix coverage. Unfortunately, nothing is that simple, and upon digging deeper, it is apparent that not all environments are available for certification. You will have some critical use case gaps, there’s no way around it. So what are they and how do you get around them?
Every automation tool just provides a way to navigate >> identify >> perform >> repeat. So before moving further on our Selenium series, let’s look at the most common Page elements & User actions to automate.
On 3-April-1973, the first mobile phone call was made by Martin Cooper of Motorola. Let’s track the evolution of Mobile Apps as a necessity today.
HP UFT provides a COM interface that allows automation of UFT itself. This Automation object model enables user to write code to perform the core UFT tasks.
If you have segments of code that needs to be used several times, you may want to create a function and then call that function from within the main action.
Since the time Android rose to power and an era of smartphones began, users have been dealing with a serious and sometimes annoying issue. Limited internal storage capacity has been a matter of concern for the smartphone users since time immemorial. Many have a SD card slot to expand the storage. SD cards are inexpensive and can be easily moved from one device to another. However, android apps are downloaded by default to the internal storage, which can fill up quickly.
Today’s mobile applications deliver complex functionality on platforms that have limited resources for computing. The movement towards mobile devices has brought a whole different set of challenges to the testing world. Mobile users are not forgiving and finding an issue out in the wild might mean leaving the application for good. Diversity presents unique challenges that require unique testing strategies.
Why was this not tested? Aaah! QAs were accustomed to testing Apps only on a selection of devices, but carriers required more money for procurement. OMG! Mobile Testing is completely different compared to Desktop Testing. If we understand the distinction and challenges of testing Mobile Apps, it will be a bit easier to tackle.
Independence & Freedom – everybody likes it. Wants it. Fights for it. And finally celebrates it. It gives you the objectivity to express your views & opinions. It is essential for a thriving society where the mind is without fear & the head is held high. As India celebrates its ‘Independence Day’ on August 15th, let’s see what it means for a Test team.
The world is driven by beliefs. It may be in God or Technology. Over a period of time every society lay down a set of philosophies or values for better organization & operation. Similarly, any technology has its own fundamental principles which have been proven right as the time elapsed. ‘Software Testing’ is no different – it also has a set of 7 fundamental principles that are proven right over the time.
Will you start testing in parallel with development or only after the development is completed? What about testing at the code-level? i.e. code reviews to ensure best practices are followed. Will it only be reviews or will you actually run the application to identify defects? How about utilizing some automation tool to ease the process? Or will it be hybrid?