Databases
StackOverflow2013
Postsdbo
POThinking about unit tests structure
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POThinking about unit tests structure
    primarykey
    data
    text
    <p>I am thinking about how to write tests for my project. At the moment, tests structure is like this:</p> <pre><code>RealClass { method1; method2; ... } </code></pre> <p>and exactly same test class structure: </p> <pre><code>TestClass { testMethod1; testMethod2; ... } </code></pre> <p>But, I do not like it, because I am putting too much test cases in one test method... </p> <p>May be I should use structure like this: </p> <pre><code>TestClass { testMethod1Opt1; testMethod1Opt2; ... testMethod2Opt1; ...} </code></pre> <p>How are you writing Unit tests?</p> <h3>Example of my test code: (Very simple test)</h3> <pre><code>public void testIsAppUser() { // My (Artem`s Zinnatullin) uId final long artemZinnatullinUId = 172672179; try { assertTrue(usersApi.isAppUser(artemZinnatullinUId)); } catch (Exception e) { fail(e.getMessage()); } // Pavel`s Durov uId final long durovUId = 1; try { assertFalse(usersApi.isAppUser(durovUId)); } catch (Exception e) { fail(e.getMessage()); } // By default uId == current user`s (who has authorized) uId try { assertTrue(usersApi.isAppUser(null)); } catch (Exception e) { fail(e.getMessage()); } } </code></pre> <h3>What I am thinking about:</h3> <pre><code>public void testIsAppUser1() { // My (Artem`s Zinnatullin) uId final long artemZinnatullinUId = 172672179; try { assertTrue(usersApi.isAppUser(artemZinnatullinUId)); } catch (Exception e) { fail(e.getMessage()); } } public void testIsAppUser2() { // Pavel`s Durov uId final long durovUId = 1; try { assertFalse(usersApi.isAppUser(durovUId)); } catch (Exception e) { fail(e.getMessage()); } } public void testIsAppUser3() { // By default uId == current user`s (who has authorized) uId try { assertTrue(usersApi.isAppUser(null)); } catch (Exception e) { fail(e.getMessage()); } } </code></pre> <p>Give me advice please.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAmarnath
    1. USArtem Zinnatullin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POThinking about unit tests structure
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COSince Junit 4 you can use parameterized tests. However, TestNG has even better with its @DataProvider.
      singulars
      1. POThinking about unit tests structure
      1. USfge
    2. COIs it really needed to catch exceptions? You're not creating an environment to use: you're testing whether or not everything works. An exception is a sign something fails and it will show in your testresult either way. Other than that: use Parameterized tests if you want to check one method with multiple values.
      singulars
      1. POThinking about unit tests structure
      1. USJeroen Vannevel
    3. COUnfortunately, I have to use JUnit 3, because Android Test Project supports only JUnit 3 :(
      singulars
      1. POThinking about unit tests structure
      1. USArtem Zinnatullin
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload