Verifying the behavior of a software system against the expected behavior of that system.
0
votes
1answer
139 views
Testers With No Experience/Programming Skills [duplicate]
We've got a bit of a problem in the company and not really sure the best way to handle it. We have a small programming team putting out incremental releases in a legacy system that is somewhat ...
2
votes
2answers
83 views
Equivalence partitioning understanding A<5 and B<5
I do not understand the following example. It says that a function X will be executed if either of A and B variables will be lower than 5. The go on and explains that there are three valid equivalence ...
3
votes
1answer
97 views
How to deal with the notion of time in UI/Integration tests
There are some well-known techniques for dealing with the notion of time in unit tests. These allow you to write unittests that always work with a specific time so the outcome of the test is ...
-1
votes
0answers
40 views
How to use CTest on a remote device
I am considering the adoption of CMake. But there is one aspect with deploying tests that is still unclear to me.
Going through the tutorials, I notice that tests are very easy to write.
# Tests
...
2
votes
2answers
160 views
What are the different meanings of 'fixture'?
I have some difficulty understanding the concept of "fixture". I know what a test suite is, a test case, a test run,
but what exactly is a "fixture"? A parameterized test case?
It seems to me that ...
-1
votes
0answers
23 views
Doing e2e testing with native applications [closed]
I come from a web background and one of my projects in school requires me to build a native windows application. I am not very familiar with writing GUI applications in MSVS and was looking for a tool ...
0
votes
0answers
52 views
Test Driven Development vs Behavior Driven Development [duplicate]
I am a developer for 3 years and preparing to dive in TDD but then I heard about BDD and the world is talking about it. I don't know which is suitable for which time? Is BDD only applicable for ...
0
votes
0answers
31 views
Assert equality in mstest when types may differ
I've been working on some MSTest automated test infrastructure, that is testing a tool that merges data sets into SQL Server database tables. The basic structure of the test is to:
Define the ...
2
votes
2answers
160 views
Who fixes broken tests? [duplicate]
Our small team has made the curious observation that diagnosing and fixing broken automated tests is a useful activity; in particular, if the CI build indicates that developer A's last check-in broke ...
0
votes
1answer
39 views
Using a flag in in-memory-repository to indicate update to entity
I'm about to write a lot of test for my application. While some of the tests check whether everything works if the user enters the right data, most of them deal with wrong/missing data. In these cases ...
1
vote
1answer
50 views
Can AspectJ or AOP in general be used to test exception handling?
I'm reading a book's chapter ("Controlled Exception Test" in "Testing Object-Oriented Testing") about testing exception handling in a running system (not at unit level). The conclusion is that it is ...
1
vote
2answers
112 views
Understanding unit testing for dynamically changing condition
I was trying to understand how to write unit tests for a few days now. I'm confused with following scenarios in the existing code.
In first function the max value changes depending on the object ...
1
vote
3answers
222 views
Should you write automated tests to check that data is correct (the contents of config files, databases, etc.)?
Simply put: is there a best practice for whether developers should write automated tests to check that data is correct (the contents of config files, databases, etc.)? If so, what is it?
Assume that ...
-1
votes
4answers
126 views
How to use unit testing? [duplicate]
How to use unit testing?
There are a lot of frameworks for different languages, which provide functionality of unit testing. There is a lot of information on how to use each of them technically. Just ...
7
votes
3answers
276 views
Doesn't single-assert unit testing break the DRY principle?
Whenever I write unit tests I have always tried to have a single assert per test to make debugging easier when tests fail. However as I follow this rule I feel like I am constantly copying the same ...
