Databases
StackOverflow2013
Postsdbo
POUnit testing static method which uses a resource bundle
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUnit testing static method which uses a resource bundle
    primarykey
    data
    text
    <p>Ive read so many articles on using Powermock and Mockito and tried so many different ways, but I still cant figure out the way to unit test the below static method.</p> <pre><code>public static Map&lt;String, String&gt; getEntries() { Map&lt;String, String&gt; myEntriesMap = new TreeMap&lt;String, String&gt;(); ResourceBundle myEntries = ResourceBundle.getBundle(ENTRIES_BUNDLE); Enumeration&lt;String&gt; enumList = myEntries.getKeys(); String key = null; String value = null; while (enumList.hasMoreElements()) { key = enumList.nextElement().toString(); value = myEntries.getString(key); myEntriesMap.put(key, value); } return myEntriesMap; } </code></pre> <p>The code is part of a (legacy) class containing about 30 static methods like this and refactoring is not really an option. Similarly in some other static methods, DBconnections are being retrieved.</p> <p>Eg : How do I mock the resource bundle ENTRIES_BUNDLE and unit test this method ? I am looking for a pattern that could be applied generally to all the static methods.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USuser2706486
    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
    1. This table or related slice is empty.
    1. COYeah, this method isn't really unit testable in its present form. Not because it's static, but because of the call to `ResourceBundle.getBundle`. In theory, you could do it with PowerMock, if you really had to, although refactoring would be a much better option. But I look at your question and I wonder why you are unit testing a legacy class. Surely, if it's a legacy class, then most of the opportunity to benefit from unit testing has already passed? And if you're not allowed to change it, then what will you do if your testing uncovers a bug?
      singulars
      1. POUnit testing static method which uses a resource bundle
      1. USDawood ibn Kareem
    2. COThanks for your answer. I agree with you completely about the value derived by writing Junits now. The thing is we have this project and part of the code is covered by JUnits and part of the code is not. The idea is to bring the whole code upto date with Junits and cover new development also with unit test cases. The code being legacy and being tested and stable, is the reason we dont want to refactor it (at least at this point in time). But having said that, and looking at your comment, it would be very helpful if you could point me towards how to do this with Powermock.
      singulars
      1. POUnit testing static method which uses a resource bundle
      1. USuser2706486
    3. COI am going straight to mock hell for this - but https://code.google.com/p/powermock/wiki/MockitoUsage13 has information about how to mock static methods. About one screen down from the top. But honestly, try Rogério's way first if you can.
      singulars
      1. POUnit testing static method which uses a resource bundle
      1. USDawood ibn Kareem
 

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