Hot answers tagged

4

"Testing", "validation", and "verification" are just words that people attach to different kinds of practices. Some of those practices focus more on "Did I build it right"; others focus more on "Did I build the right thing." You can name and group those practices in different ways depending on what you are trying to accomplish. If you want to be clear ...


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 risk of rehashing previous threads, verification (according to ISO12207) is ensuring the correct processes and standards are followed and that all requirements are traceable though the lifecycle, not the testing of actual requirements. Testing is a validation activity - you are validating the code against the requirement. At the end of the day, your ...


2

Did I build it right (verification) and did we build the right thing (validation) is the best way to explain the difference to our new (and mature) engineers. Remember that validation happens over the entire lifecycle. Acceptance Testing (verification) also contributes to the validation of the product. Once a product is accepted or bought off as meeting the ...


2

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


2

This link can provide you some guidance on IT requirements for regulatory compliance such as SOx, HIPPA, etc. http://www.metricstream.com/insights/IT_sys_val.htm


2

I think you should research about CMMI for Acquisition: http://cmmiinstitute.com/cmmi-solutions/cmmi-for-acquisition/


2

The short answer You've been tricked into asking the wrong question by a process that is not designed to actually provide you any guidance your day-to-day tasks. See the pithy Q&A on the Programmers site for a pragmatic take on this: http://programmers.stackexchange.com/questions/175393/iso-12207-verification-of-integration-and-unit-test-validation ...


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

A national standards body sent me a list of standards.. buried in there are references to: ISO/IEC 90003 "Software engineering - Guidelines for the application of ISO 9001:2000 to computer software" and ISO/IEC TR 90005 "Systems engineering - Guidelines for the application of ISO 9001 to system life cycle processes" which, at the very least, implies that ...


2

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


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

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

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

My thoughts are that this is more about the differences between static and dynamic than analysis and testing. My own personal definitions are: Static testing = Testing of requirements, designs, specifications, log files, configuration files etc. Dynamic testing = Testing of the application whilst it is running. Likewise, Static analysis = Analysis of ...


2

The first document appears to be the last draft version of the published (expensive) version - in fact, this page states that and appears (to my reading) to be recommending that you use the draft: http://www.testingstandards.co.uk/bs_7925-2.htm What reasons do you have for using either standard at all? Neither will help you to fulfil your stakeholders' ...


2

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


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

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

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

Let them meet (or do an online call) and do a handover: Explain internals Installation documentation Build documentation Deploy documentation The most important thing is that it should be complete and the new developer should be able to build it without to much hassle. Also I suggest you place the actual code in some sort of version control systems if ...


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

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


1

Simple difference in both Validation and Verification is: Validation is to check "did we build the right thing" or to check the expected results. Validation goes throughout the product lifecycle at different statges; from requirement to design to CAT(customer acceptance testing) Verification is Validation of Validation. To find out whether something going ...


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