Hot answers tagged

25

I've seen TDD/BDD/ATDD used interchangeably with Scrum/Kanban/Agile, so the confusion is understandable. Here's my take on the differences: Waterfall is a software development methodology where each kind of development activity happens in a separate phase (requirements gathering, design, development, testing...). Typically, waterfall projects work best ...


12

Same thing. No doubt there are companies that use those terms to mean different things, but their usage is not universal. If someone asks you that question in an interview, you should be able to say, "Where I work, the terms are interchangeable. Do they mean something different here?"


11

Automated tests are tests that can be run automated, often developed in a programming language. In this case we talk about the individual test cases, either unit-tests, integration/service or end-2-end tests. Test automation is a broader concept and includes automated tests. From my perspective it should be about the full automation of test cycles from ...


7

Latent Bug : A latent bug is a bug which is present in the system from previous iterations or release (in your scenario Sprint 1). They are either low priority bugs, which either went undetected or were not reported. Here is a good description : What is a latent bug? Golden Bug : If a bug happens to appear, in every iteration or release, affecting the ...


6

Kanban and Scrum are Agile process frameworks and therefor have short iterative development cycles as compared to the longer separate phases of waterfall projects. Agile projects focus on getting a working product in short iterations, each iteration should deliver a piece of deploy-able product. BDD, TDD and ATDD are not development methodologies and can be ...


5

I think the test-case is the what and the test-script is the how of the test. Its possible to defined high level test-cases to describe what needs to be tested. The test-scripts contain all the detail to really execute the test.


5

Verification answers the question: "Are we building the product right?" Does it conform to its specification? Validation answers the question: "Are we building the right product?" Is it doing what the user really needs/wants? To answer the question, it depends on the nature of the defect. If you confirm the fixes for defect now allow the product to ...


5

Task: A task (in layman terms) is basically a piece of work which needs to be done/accomplished. This term is not only used in Software Industry but also in other industries and organizations e.g. in Banks everyone is assigned some tasks of Teller, Approving request, opening accounts etc. As per the business dictionary task is defined as 'The smallest ...


5

Bug, Defect, Issue, Fault, Incident, Ticket are all the same and are interchangeably used in organisations. People can debate and say they agree or disagree and quote references but the ground reality is, it does not matter what you call it as long as it is tracked, referenced as needed and ultimately fixed. My experience shows below: In Bugzila you will ...


4

Kate's answer is great, but I want to throw in my 2 cents for differentiating TDD/BDD/ATDD. TDD is writing tests first and letting those tests drive the development of your application. This introduces the idea of Red/Green/Refactor. The basic process is to: Write a failing test Make the test pass with application code Refactor the application code for ...


4

For any terminology in SQA check official documentation "Standard glossary of terms used in Software Testing" v2.3. From the document we can see that: Use case: A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an actor can be a user or anything that can exchange information with the system. ...


4

This type of testing is known an: Extract Transform Load .. or ETL testing for short. ref: ETL testing- checklist for testing


4

How about the definition as on the Wikipedia: Code review is systematic examination of computer source code. I think the main added value of code reviews is knowledge sharing and not finding defects. That's why I would like to add a bit of more text, how about this: Code review is systematic examination of computer source code with the goal of sharing ...


3

Verified: Adj. 1. verified - proved to be true; "a verified claim" I think validated means the same, both are used for confirmations. In this case the sentence should be: Defect XXX fixes have been verified. Since its not the defect that is verified, that would mean it was reproduced, but you want to say it was resolved correctly. Personally ...


3

The difference between Waterfall methodology and an iterative methodology (agile, Scrum, etc.) is that Waterfall requires each step of a defined process be performed to completion in a particular sequence. In an iterative methodology you complete small slices of the problem at a time by gathering just a few requirements and coding each one to completion, ...


2

How about somethings like: minimized failure reproduction set Googling for this I found some research people are doing tring to automate this: https://www.st.cs.uni-saarland.de/publications/files/burger-issta-2011.pdf


2

HW revision X, Firmware 1.1.3 etc. I use the term 'Environment'. It looks like JIRA does too, source.


2

Pilot testing is when a select group of end users try the system under test, before deployment, to provide feedback about the product. Limited users use the product in pilot testing, and product is installed at the end customer to validate once the product is ready for the production in beta testing. Beta testing is is done at the client side (last stages ...


2

I think the two tend to be interchangeable but if you are studying for the ISTQB Foundations exam they will give specific definitions for each one. Also, from my experience people in your team will always ask for test cases, I've never actually heard test scripts being referred to. (outside of Automated Test cases/scripts)


2

BVA and unit tests It depends on when and how the developer implements the unit test. If the developer writes the test first (as recommended by test driven development, TDD), it's a black box test, because he doesn't see the implementation. In that case, the test conditions can only be based on the software specification. If the developer writes a unit ...


2

Any distinction made between them will be specific to your company, maybe even to your group in your department, in your company. There are some people who claim there is a clear difference, e.g. this one: A bug is the result of a coding error A defect is a deviation from the requirements or that one: A bug is getting a problem at the ...


1

I don't think there is an official terminology name for this. Suppliers seem to use the term Image based testing as here on the VNC Robot site. Also note SQA.SE already has a tag for image-based-testing, making it the most obvious choice. But after searching for a while I think I would stick with Image-based Recognition Testing, because its a bit more ...


1

There is a thing called "Perceptual diff", so I would call it "perceptual". In order to ensure that code changes do not change the look of previously rendered scenes, the renderer, utilities and shaders are tested by an automated batch process every night. ... A reference frame would be rendered and stored as a canonical image. Then, when any code ...


1

Some linguistic analysis might also help clarify: Automated Tests - in this case, "Tests" is a noun; the test is a thing. "Automated Tests" are particular types of tests; ones whose execution has been automated via some kind of code so that a person does not have to manual execute the test. You can have 1, 2, 3.... hundreds of automated tests. Test ...


1

Different terms ad terminologies have different meaning to people. It depends on an individual's understanding and thought process as to how they perceive, understand, accept and use terminologies, methods, processes or anything for that matter. Why don't you describe here what Boundary Value Analysis means to you and why?


1

I would consider it to be integrated testing. You have different areas of functionality in the organization. The different areas have team of people supporting them. Each team will test their part of the product or system and then rely on other teams to do their part. The problem is that there are interactions between them and that these interactions ...


1

Regarding bug-reports: In my opinion, the best possible bug report (assuming that the person that sends the error report does not know the causes of the observed failure) is a bug report with reproducibility information, so that the developers are capable of reproducing the problem. In several bug tracking sites, for example MySQL, we find literally ...


1

Since the difference between "Incident" and "Defect" treads on a very thin line. They are often confused to be same. In nutshell, all defects are incidents but all incidents are NOT defects. The TIR contains the details of actual vs expected results and any other investigation points(why the test failed,impact of the failure etc) According to IEEE, it is ...


1

An incident is just something that did not happen as forecasted. It can be because : The tester didn't do the scenario properly. There is a technical bug. There is a functional bug. Before even thinking about reporting, the tester must investigate as far as he can(how far depends greatly on the shop), and at least chek the error does not come from ...


1

Basically an incident can be a defect or can be a feature. During testing you log suspicious behaviour which you cannot state for sure as a bug and only after further investigation can be titled as defect. In the defect report will be links to features/design specifications/discussion which provide enough evidence on deviation from it.



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