I am not going to spare her. She has rejected 7 bugs, I reported, within last three days. I know she is using personal grudges as professional sword……
A teammate was fuming and the discussion suddenly caught fire when a couple of other teammates joined in sharing the same experience with other developers. The team meeting turned a discussion point about bug rejection. After some discussion, we all decided to do a simple exercise to save ourselves from the humiliation of bug rejected, in future.
The most important factor for test environment is to replicate it as close to the end user environment as possible. Commonly, end users are not expected to perform any configuration or installations by themselves as a complete product or system is shipped out to them. Hence, by Continue reading →
Test Bed / Test Environment Setup Challenges and Best Practices:
On several occasions, the testers find their defects getting rejected for environmental issues or they find themselves constantly replicating the defects for the similar reasons. While opening the most number of defects must certainly be one of the personal benchmarks for every tester, most testers must also emphasize on having the most number of valid defects.
How is this achieved? Apart from the other aspects like planning a variety of test scenarios and understanding the line item thoroughly, Continue reading →
The conference room was silent and every face was staring at me. Just ended client call left all of us clueless about how we can rectify the mistake. Client was very unsatisfied and he was thinking that the product was not tested at all. When my manager tried to argue that all the functionality were working well, he cut shot him saying “What is the use of functionality, if users are not able to install the product?” We were stunned.
We borrowed two hours of time frame to look into it and finished the call. But no one moved out. Everyone was asking a question – How can it happen? Why we did not catch it?
-> Have you ever been in a situation where you’re out of college and hired by an organization for the role of a Quality Assurance Analyst or in general terms as a “software tester” instead of a developer?
-> Have you also been advised time and again by a bunch of people called “seniors” to opt for a project that will provide you Software Development experience instead of testing?
-> Have you been told that it’s okay to be a tester in the initial phase of your career, but later you must move to a development role or Continue reading →
Having been in the software testing industry for about 10 years now, I have had the good opportunity to witness first-hand the movement of the industry in this relatively short time span. When I started out, software testing was just beginning to make its importance known and have just recently upgraded from a ‘should do’ to a ‘must do’, regardless of what the software development lifecycle said.
Software testing, in the past, never had a big follower-ship due to the cost incurred. In order to perform testing activities – people had Continue reading →
Onsite offshore model is a very common working method for many IT teams across the industry, especially the QA teams. The way this works is, one/more (depending on the magnitude of the project) of the service provider’s QA team member works along with the client at their location.
The client location and the service company’s workplace can be geographically any place – across the globe or sometimes in the same city.
When this is the working model, there are some expectations from the Onsite and Offshore resources respectively. Let us see what they are:
This will be basic “how-to” article and is not any automation tool specific. Basically, what I am trying to do here is put the thought process that goes into creating an automation test case into words. As always, I hope this will be useful to you all.
How to design an automation test case or script?
Automation always follows manual testing. Typically, one or more rounds of manual testing already would be performed on the AUT. This implies that manual test cases already exist and have been executed at least once.
Software Process Engineering Software Engineering is a discipline that aims at producing high-quality software through systematic, well-planned approach to software development. It contains many good practices, following the standards to achieve the quality product. The three main phases of Software Development are Analysis – Design – Implementation. To accomplish high-quality software is essential to produce the defect-free product.
The defect is the unexpected or undesired behaviour that occurs in the product. Anything related to defect is a continual process, not a particular state.
Defect Management Finding and fixing the defect in the early stage of the software development reduces time, rework and money. Finding the defect in later stages always costs multiple times than early stages. It enhances the quality by adding reliability, portability, maintainability etc. Hence it is advisable every company should go with defect management system and defect management team at every stage of the development to attain the good quality in products and to gain the customer confidence.