Hot answers tagged

4

Consider using A/B testing on your site to determine the impact of response time differences to your customers. If done well, you will determine If performance differences really matter How much they matter Thresholds after which your customers abandon your site


2

At first let's look at the definition of functional requirement term from ISO/IEC 27000:2014 standard: functional requirement requirement that specifies a function that a system or system component must be able to perform — So functional requirements are what software should do. Then, coming back to functional suitability degree to which a ...


2

You can think of a product as someone's attempt to satisfy a list of requirements. Ideally, those requirements are someone's attempt to solve an actual problem. From a myopic point of view, QA is about verifying that a product satisfies requirements. But the definition quoted in the question points to a deeper definition of quality: whether a product ...


2

ISO 25010 is an updated revision of ISO 9126. Security is considered non-functional.


2

In general, a test case is a pair of an input and an expected output (or as many books say, it mostly has just a single step: do sth and check it). A test case or a simply "a test" is an experiment we run in order to reveal some information about a product or service. one often has to follow certain actions/steps Only if you are taking the ...


2

Software quality analyst is responsible for applying the principles and practices of software quality assurance throughout the software development life cycle. Some of the tasks of software quality analysts are:[citation needed] Participate in QMS management review meetings. Approves the QMS documents of which QA manager is the main author. Undertake ...


2

Is it acceptable to re-define boundaries from functional to testable? It depends. If you are testing a value that represent a physical property you can safely limit yourself, although it is a good idea to document it somewhere and double check your assumptions (see the first F16 flights at Dead Sea heights of far below 0) In your case I would invest ...


2

Should I create some linkage in my documentation so that the same inputs are avoided across different scripts? Yes, you should create the same to avoid repetition of input data and expected results. Doing this your number of test cases will get reduced to required value, this will save you execution time and test case maintenance effort. Should I ...


2

Measuring response times in realistic conditions For most organizations, it is not worth the trouble to test your site against the variety of latencies and network speeds you see in production. This is particularly true if you are measuring not just the server response time but the total page render time. The latter depends on a lot of factors, including ...


2

I do not recommend relying on ISO-9000 for guidance on software quality. ISO-9000 describes a heavy-weight procedure for how companies document all their processes. That is all; it does not address how to create quality. ISO-9000 makes a lot of sense for manufacturing. If you run a factory, and your employees do not have a shared understanding of how ...


1

Ideally acceptable response time ranges should be specified in SLA or NFR. If they aren't - you need to make an assumption for how long end user will have to wait which may be minutes for i.e. in-house internal application or not more than few seconds for e-commerce websites where user will go away if the site operates slowly or down and will never come ...


1

This is a situation where a set of test data designed specifically for unusual/rare test scenarios comes in handy. The way I'd deal with your situation is this: Set up two or more extremely high-priced items (preferably at a little under the maximum allowed price for a single item in the system). If your POS system allows quantity limits, ensure the ...


1

Having gone through the CMM adaptation I'll point out that it isn't just what is inside the QA process that matters. The QA process needs inputs and outputs and having a formal (written) process means that the inputs and outputs must be standardized as well. Having QA is one of the first level of processes that needs to be developed when improving an ...


1

I've had the same request a few years ago indeed. The company I am working for decided to set up a dedicated QA dept. After an initial period of research we decided to adopt an international standard, in particular ISO 9001:2008 (we are now TUV certified). The standard is not a step by step guide and sometimes it is really difficult to understand how to ...


1

To put it simple: QA is a process-oriented activity - evaluation, review and improvement of processes across the software development life cycle. Better processes=>better product (quality). QC (Quality Control) is product-oriented and involves dynamic testing and static techniques such as reviews, inspections etc. Products are e.g. specifications, design ...



Only top voted, non community-wiki answers of a minimum length are eligible