10

There has to be some sort of pain point to make Management and front-line employees aware of the need for testing. How your company does that depends on how mission or life-critical the software truly is. The typical Developer/Tester ratio in an unregulated development shop is anywhere from 4:1 to 8:1. NASA uses a ratio of 1:8. That's right, each Developer ...


5

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


4

ISO 15288 covers the System lifecycle, while ISO 12207 covers the Software lifecycle. As of 2008, the two are "harmonized for concurrent use". For instance, 12207 can be used "either alone or in conjunction with ... 15288" In a bit more detail, what this means is that 15288 covers all aspects of developing a system, where examples of system components are ...


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


3

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


3

To improve quality for a software product we are splitting up quality into internal and external quality. Spread over three quality groups. It gives a more detailed view on the different quality aspects that are relevant in software development. External quality determines the fulfillment of stakeholder requirements and internal quality determines the ...


3

I'm going to start with the flippant answers before I give you the real ones. The flip answers are no less correct, they're just not something you're likely to want to hear. There is no standard because it's a meaningless metric. There is no standard because it's a meaningless metric. There is no standard because it's a meaningless metric. Now for the more ...


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

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


3

I'd highly recommend you take a look at the Airbnb Style Guide. Although, it's a little long and has some subjective rules, you can easily pick out your favorites and apply them to your code reviews. Also, it's nearly impossible to remember all the JS rules and best practices so while you're coding I'd really recommend you use a linter like eslint. You can ...


2

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


2

I think that it is important to understand the difference between testing and QA. There is one post you need to read on the topic by Michael Bolton, Testers get out of the QA business. The short version is that testers, who don't change code, are assisting with quality, not assuring it.


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

+1 for it depends If the upload operation in your example can only be done through the mentioned failed menu than it is difficult to not fail it. OTOH maybe you are part of the "upload team" and all you want to do is verify this small operation and not end to end integration, so failing the test is out of the question Another approach (I use it with ...


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

From application perspective you need to look at below states for DB to be validated with basic cases Clean up Scripts (Clearing Previous Run Data) Initial Data population (From a fresh install whatever initial configuration you need to do) Prerequisites Validations Tests (Checklist to validate before you start run - Services up / DB's accessible, able to ...


2

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


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


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


2

There is no quantitative measurement for 'reasonable'. We will always disagree about what reasonable means. When using an application that is of no consequence to me, my tolerance level will be around 1s to 2s. However, my tolerance level will be much higher when I’m dealing with my bank (they have my money). However, the measurement of response times, is ...


2

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


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

Tools and techniques allow you to test in a specific way (depending on the tool, or on which technique used). They will produce correct output (as in: the product has been verified correctly by using such a tool/technique). Procedures and standards make sure every individual will test in a similar manner (regardless of which tools/technique is used - or ...


2

Testing culture can only be changed with support of upper management. If management doesn't support you, then you won't be able to change the culture. So you have to make a case to management that testing should be prioritized. Try to build the testing as a part of the SDLC. Otherwise, people will always cite deadlines and release cycles as the reason ...


2

My personal take: At a high level Test the API Endpoints, Status Codes and Data with Smoke, Happy and Sad Tests At a detailed level one needs to ask the following questions. The answers will guide what and how to test. What documentation exists ? What functionality it provide ? Does it support concurrency ? What are the API endpoints ? Is the API internal ...


1

It is hard to adhere to a single standard as software performance testing has to be tailored to their contextual environments. Software performance testing has relatively vague requirements, as performance testing does NOT target functional quality, instead, it targets software's structural quality. For example, we use performance testing measure efficiency,...


1

You can look at this from the product vs process perspective: is "not following the standard" a product or a process problem? It is a process problem because the issue is that the process/policy/guideline was not followed. So ensuring that the standards are "correctly implemented" and "followed" are both QA jobs. The confusion might have arrived because in ...


1

I have used ISO/IEC 90003, which discusses how to implement ISO 9001 for Software Engineering as a guideline for areas that should be covered in a process. There are a number of sections that discuss "release" depending on how the software is deployed.


1

The main difference it that requirements are what has been written down in the requirements documents, both the top level requirements document as supplied by the customer and in the derived requirements documents generated during the development process. This does indeed differ from stated and implied needs in that there may well be implied needs that ...


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