I don't think there's a special name for this particular situation. Nor do I think we should create one. I think we should try to keep things simple, rather than layer more artificial names of top of what we currently use.
We have established automated tests but it is not uncommon for them to fail against qa.
(we can fix them later, but different ones ...
The terms in software world doesn't usually have a well regulated definition , it is more about understanding the concept and having an organised approach to testing than testing what ever comes to our mind.
so don't need to break your head over these definitions , just remember the below
One of the reliable definitions you can refer is from ISTQB glossary: ...
Yes, you can and maybe you should depending on the context. If you write code you are a developer, or programmer. Writing automated tests is coding in most cases. Look at this definition of programmer.
A computer programmer, sometimes called a software developer, a
programmer or more recently a coder (especially in more informal
contexts), is a person who ...
I'm not entirely sure if this is on topic or not. I mean, on the one hand it is because it has to do with testing. On the other, well, I'm not sure if it's actually answerable - but I'll give it a shot.
Whether you call yourself a developer or programmer or coder or software engineer is entirely up to you. You can put anything you want on your resume and it'...
The use case you defined is "Absence of error, fallacy"
Meaning the software product has no bugs , it has no errors but the feature it self is not what user want . It creates an illusion of stable product but actually is just "fallacy"
a failure in reasoning which renders an argument invalid.
So in your case you can use below ...
"Quality is value to someone (who matters)", Jerry Weinberg.
The three points talk about not delivering value to some of the people who matter.
Thus you can say the application is of low quality to those people.
Test each part of the program to justify that the individual parts are correct.
It can be performed at any time
Does NOT verify whether your code works with external dependencies correctly.
Define the behavior of a single module.
For example: Testing of a tool that downloads images from the internet and able to modify them. Here the first unit ...
Yes termiology is viral and has different meanings to different people. It's always a good idea to set the standards for terminology and then hold education sessions on what inter-department agreement.
You'll need buy-in from Managers, Product Owners, Developers, QA Team. Once an internal written document describes the meanings then the fog will lift.
Corner Case testing: Sticking to the definition, corner case testing is testing multiple parameters for extreme levels, as the user sticks to the corner of the configuration space.
Boundary case testing: When working on boundary testing, users have to test the system for extreme ends or boundaries of the input values. These usually include start-end, maximum-...
Accessibility Testing is a crucial testing type within Usability Testing as a whole (according to ISTQB Syllabus)
Target audience for Accessibility Testing:
Users with disabilities (any form of disabilities)
Target audience for Usability Testing:
Common users of those applications
Types of testing items/process conducted or performed part ...
In qa company, various defects have been verified by QA team. Both the terms are correct if the defect is working fine with no new issues.
But if the defect fix change the behavior of feature to fulfill the business requirement then we can use term "Defect XXX has been validated." along with the issues found during defect validation.