7

The terms “performance requirement” or “performance attribute” are preferred over “non functional requirement” according to the most recent update of The IEEE Standard for Software Quality Assurance Processes 730-2014 Definitions. The IEEE Standard for Software Quality Assurance Processes 730-2014 defines Performance requirement as the measurable criterion ...


6

A web search of the terms resulted in, Scalability Testing, is the testing of a software application to measure its capability to scale up or scale out in terms of any of its non-functional capability. Performance, scalability and reliability testing are usually grouped together by software quality analysts. The main goals of scalability testing are to ...


4

I recently hired on with a new company and wondered about this as well. After speaking with my former and current supervisors, I got the following advice and followed it. Know what you're talking about. Assuming the person interviewing you is a Test Manager or experienced tester, they know what they are looking for. They're ears will be open for key ...


3

Some points would include, Battery back time. Screen resolution. Its weight. Its dimensions. What accessories come along with it. ... And you can keep on going with your list of expectations.


3

In regards to you screenshots in general and Summary Report in particular, as per The Load Reports guide the explanation of the report fields is: # Samples is the number of samples with the same label. Average is the average time of a set of results. Min is the shortest time for the samples with the same label Max is the longest time for the samples with ...


3

There will be longer and doubtless more complete answers but I think that if you understand the core principles of testing, you'll be fine. Know what the product is supposed to do. Determine if it does it. What is the product supposed to achieve. Does it achieve it? Those are the Golden Rules. Everything else can be thrown away apart from those. ...


3

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 ...


3

This is a pretty common practice. At Microsoft we called it a bug bash I have also heard it called a bug hunt, I'm not sure if the industry has a standard term for it. Yes, I and many other teams have done something similar. Yes, we nearly always got some good data out of it. As many people as we could get, usually for a few hours (1-4). We normally got ...


3

First, you're going to have to understand the Project Managers and Developers that you work with. Not knowing them it is hard to understand what sort of arguments might persuade them. Think back on arguments you've had with them, what kinds of arguments did they use to try to persuade you. In all likelihood a similar form of argument will likely hold ...


2

You need to connect the dots. There are at least three messages to convey: your production system has problems that are worth worrying about; those problems result from your shortcomings in your organization's current practices; and the best way to address those shortcomings is to introduce new tests, i.e. to use your terminology, additional UAT-level tests ...


2

Functional Suitability This characteristic represents the degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions. This characteristic is composed of the following sub characteristics: Functional completeness. Degree to which the set of functions covers all the specified tasks and user ...


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

I think UX is often miss-interpreted as design. Design is often an acquainted taste and therefor it is pretty much untestable, but usability testing is something different. It is important that user can use the product with only minimal training, but more important it should feel logical and non repetitive within the users mental model. During evaluation ...


2

Nonfunctional requirements generally support all users in that they describe the business standards and the business environment, as well as the overall user's experience, therefore, software testing is very essential for non-functional properties also. In non-functional testing the quality characteristics of the component or system is tested. Non-...


2

The best way to do this is practice functional testing and master the art. Once you do that you won't need to find back door answers to such stuff. Never try to pose yourself in an interview that you are not, because sooner or later you will get caught and that will affect your job. Learn the art and practice it so well that any question thrown at you on the ...


2

Yes, we've done something like this in the past. Yes. For many reasons - performance issues, functional issues, team spirit, etc. It's wasn't very time-consuming for us. QA, Dev, Customer Support were involved Didn't really run into any problems In addition to inviting others to participate, we used a load-testing tool to apply background load which ramped ...


2

The goal of testing is to prove that certain kinds of problems are absent from the product. But what if a test fails and uncovers that there is a problem? You want to know that as soon as possible, so that the problem can be rectified without costing the company too much money in terms of downtime, lost revenue due to late delivery, etc. On the other hand, ...


1

If not how to decide what types should be done? Ask the stakeholders. If they don't know, then you'll have to go through it them in detail, talking about how the application will be used. Is it an internal tool or external? Is being performant important or not? Is it a disaster for the business if the product ships with issues, or is it acceptable for now? ...


1

That depends on what level of what the quality degree you want to reach, what resources you have and what the initial conditions are. If you have the first draft version of the app then I does not make sense to perform Regression testing since Regression term is undefined for that build. If your app is a middle-ware service then probably Usability testing ...


1

I have no idea how many people here know anything about "CoreNLP". To me it seems you are on the right track: e.g. learning what it is. Go from there. You won't find copy/paste answers for your challenge. So ask yourself: what is it that I want to know about these functions? what do I know that function x should be doing? How could I check that thing ...


1

The wikipedia definitions quoted by @TESTasy are a good start, but I'll sum them up a bit: Capacity Testing measures how many users the application can handle. It is a subset of scalability testing, in that when testing scalability, you will get a measure of application capacity. Scalability Testing measures how well the application handles increasing ...


1

I think you could follow all the answer you can see on your post. I will also recommend you that start by learning a programming language (which you feel more confortable) and then start using Selenium (which is easy to start). Once you control Selenium, start using Jenkins along with your test developed on Selenium and upload all of them into a git ...


1

Often in interviews, I'm asked "how would you test x, y, z?" and while I didn't plan it, I found myself giving a pretty stock answer each time. I'll start off saying something like this: "It depends - on the features, the requirements, the timeline, and any other relevant factors." And then I'll start laying out specific examples. A web page that changes ...


1

Suggest having dedicated Non-Functional (NF) Test Management practice separate from the functional practice (UAT etc.). Also NF needs to be much more closely aligned to (i) Infrastructure Architecture, and (ii) Production Systems Management. Also have the NF testing as separate test phases with separate governance. Have used this approach successfully ...


1

I lost you somewhere along the question... Anyway, upper management are usually convinced by showing them the ROI, for example if you can show problems that could have been detected and solved during a non functional testing phase.


1

Yes. This was part of process for major releases at a former company and was done in an ad-hoc way in other companies I was part of. Yes. Apart from the reasons Joe states above, having people with different knowledge of the software combined with a different business view often resulted in issues/scenarios the development team hadn't thought of. The amount ...


1

Functional testing deals with checking the functionality of a system or application works as expected. You give certain inputs and check whether you get the expected output. You will usually use some sort of heuristic to tell whether result is expected or not. Non Functional testing deals with checking the non-functional aspects of systems such as ...


1

I don't agree with the idea that "if there is a refined specification of installation it's functional otherwise not". Thinking in that way is like "do not describe in detail your non-functional requirements or they become functional". I think that non-functional requirements need to be well specified. And they continue to be non-functional. Apologies for ...


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