Tag Info

New answers tagged

0

Yes, you can verify daoInterface.insert is called with verify(daoInterface).insert(anyObject());, but you have to mock DaoInterface first with DaoInterface db = mock(DaoInterface.class);. verify(daoInterface).insert(entity); will fail all the time because entity object from verify's argument and entity inside serviceMessage() are different instance. Instead, ...


3

There are tools that will generate a set of tests that cover every combination at least once without hitting all possible combinations (these work on the principle that most bugs will be surfaced by exercising pairs of settings). Since the feature hasn't gone live, your business analyst is probably your best reference for the combinations that are most ...


2

I think it is called a "Combinatorial test matrix" . With more combinations the matrix could become infinitely large, have a look at Pairwise Testing to simplify this, but still have a high coverage with combinations. Pairwise (a.k.a. all-pairs) testing is an effective test case generation technique that is based on the observation that most faults are ...


1

It's just a representation of test cases. When I use it I call it Test cases, Test case matrix, Test Matrix or just tests. Anyway, it is a great way to present data and test inputs.


1

If I understand correctly, you are looking at ways to make your tests more efficient, so you can get as quickly as possible to the desired state and then perform the actual assertion that the test case is intended to cover. There are a couple of options you have: Use a class setup method, or application setup method to log in, then re-use your existing, ...


0

PageObject design pattern Every test needs to log in, but code is in one place, and any test will just use it, just 1 line of code. Login is not a problem. Other stuff, to prepare application's data to certain state might be bigger waste of time (but again, can be wrapped as single pageobject call). If you log just once, then run long trail of tests, they ...


0

From Test Management tools perspective a "Test Plan" is a collection of certain test cases to be executed for a certain build. For example in MSTF (VSTS) from Microsoft and ALM from HP the term 'Test Plan' is used. Other test management tools like SpiraTest uses term 'Test Set' to refer the collection of certain 'test cases' being 'planned' for 'Execution' ...


2

If we refer to ISTQB glossary of terms then test suite: A set of several test cases for a component or system under test, where the post condition of one test is often used as the precondition for the next one. test plan: A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, ...


8

The traditional definitions would be something like this: A test suite is a collection of test cases related to the same test work. You might have a suite for regression, one for build verification tests, a suite that is specific for a component, and so on. A test plan is generally a document which describes testing approach and methodologies being used for ...



Top 50 recent answers are included