Functional testing in the verification
Yesterday my question How come verification does not include actual testing? created a lot of controversy, yet did not reveal the answer for related and very important question: does black box functional testing done by testers belong to verification or validation?
How to Be a Software Engineer? [duplicate]
This question already has answers here: Why sacrificing good software engineering practices is typically the first choice for software development projects assuming “good enough” quality [duplicate] (6 answers) Closed 9 years ago. My problem is kind of weird so please bear with me. I have been working in a start up concerned basically with mobile […]
Verification of requirements question
Doing a lot of reading about V&V, I would need to clarify the following.
A lot of definitions (less formal ones found in books) define verification like that:
Verification: The software should conform to its specification.
But then they speak about requirement verification, design verification etc. If I say that these items are “software” in terms of applying the definitions, what should I checked them against? What specification should requirements, which is the basic information, conform to?
Resurrecting a 5,000 line test plan that is a decade old
I am currently building a test plan for the system I am working on. The plan is 5,000 lines long and about 10 years old. The structure is like this:
TDD, BDD or both? [duplicate]
This question already has answers here: Relation between BDD and TDD (4 answers) Closed 11 years ago. I’m a little bit confused about BDD. I’m doing TDD currently. My question is whether BDD is complementary to TDD or it’s a whole new thing and my team should do both TDD and BDD? Or is it […]
Testing of visualization projects
We develop small to large visualization projects for different tasks and industries and sometimes while rewriting them a couple of times in the process we hit walls because we discover that we need to add a lot of code to support new requirements. Now we have established a design process that seems to work well (at least we reduced the development time for each new project quite a bit), but we’re still left scratching our heads around this question: what exactly should we test when testing visualizations?
Testing controller logic that uses ISession directly
I have just read this blog post from Jimmy Bogard and was drawn to this comment.
bug: deviation from requirements vs deviation from expectations
I am not clear on this one. No matter the terminology, in the end the software fault/bug causes (according to a lot of sources):
What is the best way to go about testing that we handle failures appropriately?
we’re working on error handling in an application. We try to have fairly good automated test coverage. One big problem though is that we don’t really know of a way to test some of our error handling.
Testing vs QA – output?
I was trying to find a relevant source of information for the above, but I failed. What is the output of software testing? Some say its “list of bugs”, others say “answer whether or not the software conforms to what customer wanted”.
I know testing is a part of QA but not sure what is its aim and output in this context.