New answers tagged

0

Testing policies for a given organization describe how the testing that it does aligns to the company's business needs. Testing - and quality more generally - is defined by the company for the current situation it is in (size, industry, purpose, etc). Best practices for testing should be examined to see if they are relevant for the given situation. If they ...


0

When it comes to software testing, testers never get to have a full set of details on requirements. From usability to functionality, performance, and security, it is entirely the job of testers to understand the project requirements and foster QA operations that can help meet every smaller and broader objective with the product. The process you have shared ...


1

I think you have made your QA engineer work on the right thing at the moment. As you said the project is going through extensive changes, I would suggest you put your QA engineer to handle tasks related to QA services like: -Exploring the project requirements and goals -Writing test policies -Define the test process based on existing requirements and ...


1

Lay a foundation for quality "For the moment, we are asking the QA engineer to go through customer business requirements and to validate the existing functionality against them as well as familiarize himself with the roadmap." That is good for a few key scenarios. However, beyond that it may lead to a testing setup that looks more like an ice ...


5

First of all, you need to define better what you want to measure. Imagine a sports team. One could say that "improving" means "winning more games" - and one could say that a software team is "improving" when the product is making more money or has a bigger user base. However, in both cases, one can break down what makes the team ...


1

when requirements and specifications are not accomplished and doesn't satisfy definition of ready for testing quite often. If you test functionality under this scenario that is the problem. Another way to put it - your organization has decided that actually it is ready enough for testing despite all the issues. Ready for testing and easy to test may be very ...


2

I would not use test cases for a database conversion project. The task at-hand is database validation to see if foreign key constrinsta have been enforced. This can be developed reagrdles of the conversion. I would use database and dba tools and programs. What to do about missing or duplicate records will depend on your target database - same vendor? same ...


4

"Good testing involves balancing the need to mitigate risk against the risk of trying to gather too much information." - Jerry weinberg Implement 3 amigos sessions I would implement precisely 3 amigos sessions in this situation to develop an shared understanding as team for below: Business- What problems are we trying to solve? Development- How ...


0

When we do the regression or sanity test we have to run the same set of test cases over and over again. Investing time of quality engineers time for repetitive work is not productive. If we automate repetitive test cases quality engineering team has time to do more exploratory testing which is creative. On the other hand we can save execution time from the ...


Top 50 recent answers are included