AUTOTECHX

  "You catch more flies with honey than you do with vinegar." Deliver the bitter medicine in a sugar-coated capsule: Most of the times, as testers we are the bearer of bad news. We will have to tell the programmers that their baby (code) is ugly. And clearly, no mother will ever want to hear such a statement [irrespective of how ugly her baby really is]. Hence, I can understand how difficult it can be for the programmers to accept the fact that their code is defective and someone else has detected it. To deliver such a bad news, you will have to do so tactfully and professionally! Hence, testers may have to be diplomatic when confronting a programmer with a fundamental goof. Diplomacy, tact and a smile on the face - all can work to the tester’s advantage and are essential in preserving a harmonious relationship with the programmers. Be unbiased: While communicating, treat programmers and testers alike (e.g. refer them as "we" instead of "you"...

“The aim of writing problem report (defect report) is to get the defects fixed” Just imagine a tester who is very efficient and skilful in finding defects in the application that he is testing but is very poor in reporting them. Is it not something like cooking a great dish but serving it in an old dirty plate that leaks and messes the dining table? What is the point of taking your time and putting your effort to prepare a tasty dish if your guests can’t enjoy its tastefulness (due to the bad way in which it is served)? The same can happen if a tester is good at finding important defects quickly but ends up logging bad defect reports/bug reports! Chances are more that the seriousness of his reported defect might go unnoticed [worst still, the defect might get turned down as “Rejected” since the programmer looking at the defect report finds it hard to figure out the bug]. Following are few pointers that can be kept in mind to effectively report software issues: 1. It’s all ...

Smoke Testing Vs. Sanity Testing “Smoke Testing” is usually done on the nightly/interim build to test its stability. Therefore “Smoke testing” is often called as “Build Verification Testing” too. In contrast, “Sanity Testing” is usually done during the later cycles after thorough regression cycles are over. When multiple cycles of testing are executed, “Sanity Testing” is done towards the Product release phase. “Smoke Testing” is done following a shallow and wide approach where all the basic and major areas are tested without going too deep into the functionality. In contrast, “Sanity Testing” is usually a focused but limited form of regression testing, which follows a deep and narrow approach to test a particular functionality in detail. “Smoke Testing” is done by developers before the build is released or by testers before accepting a build for further testing. On the other hand, “Sanity Testing” is done mostly by the testers. “Smoke Tests” are mostly in form of scripted f...

Selenium is one of the most popular open-source automated testing Tools available today. Selenium automates web applications and mobile apps for testing purposes, but is certainly not limited to just that. Introducing Selenium Selenium is a free (open source) automated testing suite for web applications across different browsers and platforms. It is quite similar to HP Quick Test Pro (QTP now UFT) only that Selenium focuses on automating web-based applications. Testing done using Selenium tool is usually referred as Selenium Testing. Selenium is not a single tool, instead it is a set of different tools each with a different approach to support test automation. Learning all the tools will give you different options for approaching different test automation problems. These tools when used together give many options for locating the UI elements and comparing expected test results against actual application behavior. The following  are the four tools that comprise the Seleni...

Agile methodology  is also called as RELEASE or DELIVERY DRIVEN APPROACH since it gives better prediction on the workable products in short duration of time. AGILE Methodology are used to develop an application very FAST and adopt the changes at greater pace. Agile is all about how to work together as a Single team to achieve a common goal (Quality). AGILE TEAM is not only suitable for the Software Developers but also for Team Leaders, Project Managers, Product Managers, Development Managers, Testers, QA Managers, QA Engineers, Technical Writers, Web Designers or anyone involves in the delivering of software. Winston Royce’s Waterfall Model  “From the 1970 IEE paper “Managing the Development of Large Software Systems” A careful reading of Royce’s paper reveals: Each phase should pass iteratively to the next The entire process should be exercised twice before release Backtracking is not possible in waterfall after analysis phase is done. No customer i...

Automation can be defined as the technology by which a process or procedure is performed without human assistance . As per ISA , the dictionary defines automation as “the technique of making an apparatus, a process, or a system operate automatically.” We define automation as "the creation and application of technology to monitor and control the production and delivery of products and services.” For better reference watch the video below:- credits: Wiki, International Society of Automation (ISA), Youtube.