Tag Info

Hot answers tagged

9

I've read that if a requirement can't be verified by black-box testing or inspection, then it's not a requirement, but a design specification. I don't think that's true. There are plenty of requirements which are difficult-to-impossible to test with black-box techniques; for example, a client-server application might have a requirement that all ...


5

I prefer to test in isolation, test should not be depended of each other in order to be able to run them on their own. This makes testing a smaller part of the application easier for developers. Also if each test has its own environment to run in you can run tests in parallel without tests conflicting each others runs. There will be some extra overhead in ...


4

There are tools that support this. SmartBear's TestComplete does - you can configure to continue after a failure or to stop after a failure - you'll find some details below about how the team at my previous employer handled dependent tests with TestComplete. I don't consider it a terrible idea - I've worked mostly with large, complex applications where it's ...


4

Systems testing is often performed against the whole platform, and treats the environment as a black box. system integration testing however, acts upon a subset of the whole system, and may mock other platforms, interact with databases, network sockets etc to evoke appropriate responses from the parts being validated. The objectives of system testing is to ...


3

In your comment you asked Lets say we have a system C which is combination of A and B (A + B = C). Now i can check perform Integration tests for A, Integration tests for B. After this i need to perform System tests on C which is the result(whole system). Where exactly will SIT come in here? In testing C, but I believe you won't learn much from short ...


3

In my vocabulary system testing would be testing one complete product ( http://en.wikipedia.org/wiki/System_testing ) and system integration testing would be testing combination of products ( http://en.wikipedia.org/wiki/System_integration_testing ). As always, it's good to make sure others are using terms in the same way and in an interview point out that ...


2

If we take a look at the definition of BVT we can't find the statement that BVT belongs to white box testing approach. Just "a short set of tests, which exercises the mainstream functionality of the application software". And for system testing -- "testing conducted on a complete, integrated system to evaluate the system's compliance with its specified ...


2

Does the presented style of cascading tests violate the "one assertion per test" principle? Yes, it does. While the style is quite clean, a disadvantage to your solution is that it becomes harder to run test_login and test_write_post with a different user, for example with one that is already registered. I personally find a better solution is to have ...


1

According to me terminologies in testing do not matter much provided the communication between the testers and other stakeholders goes successful. That is, the other stakeholders understand the reports delivered by tester and the tester understands their needs and that of the software correctly. For example build verification testing could also mean to ...


1

Here's my perspective: Unit Testing tests a single unit - usually at the routine level (that is, only one unit of code such as a function is tested). Unit tests are typically code-based, written by developers, and executed whenever the application is compiled or built. Module Testing tests a single chunk of functionality in isolation, such as testing the ...


1

The way I would test this software will be focusing on different areas: 1. unit testing or library - I am not sure whether you will have access to the code or the developers have done some unit test on the components in the software. In this phase, you can test out the functionality of the components in the software easily (without the interaction of the ...


1

I see this in Ian Somerville's book (9th edition, section 8.3): There are two important distinctions between release testing and system testing during the development process: A separate team that has not been involved in the system development should be responsible for release testing. System testing by the development team should focus on ...



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