Reading System.out Java Test

Question

I have a task to test a console application. I can access one method, but would also like to check that the string formatting is working correctly.

As this method does not return a string, but rather prints to the console, is there a way I can intercept the list printed line?

Does it even make sense to test this sort of thing?

See this: http://stackoverflow.com/questions/3228427/redirect-system-out-println — Kevin Workman, Feb 20 '14 at 16:14
Do you have the option of modifying the code you are testing, or do you have to test it as-is? — James Dunn, Feb 20 '14 at 16:20
Nope. It's out of bounds unfortunately. I am testing a method it is calling, but also want to test the output being delivered to the console. — james_dean, Feb 20 '14 at 16:21
I believe @KevinWorkman has basically answered your question. You can set System.out to your own PrintStream. (Not sure but you might have to write your own.) — Radiodef, Feb 20 '14 at 16:24

score 19 · Accepted Answer · edited Mar 27 '19 at 08:10

19

Here is a sample how to catch output to the System.out:

java.io.ByteArrayOutputStream out = new java.io.ByteArrayOutputStream();    
System.setOut(new java.io.PrintStream(out));    

System.out.println("Test output");    
System.err.println("Out was: " + out.toString());

edited Mar 27 '19 at 08:10

Gilad Green

36,708
7
61
95

answered Feb 20 '14 at 16:29

AnatolyG

1,557
8
14

score 2 · Answer 2 · answered Feb 20 '14 at 16:23

2

You can use System.setOut() to redirect the System.out.println writes to a PrintStream(OutputStream). Then you can write that OutputStream to a String and test it.

answered Feb 20 '14 at 16:23

Roberto Linares

2,215
3
23
35

AlfredoCasado · Answer 3 · 2014-02-20T16:32:40.793

The way for testing this its make a good design with a "output" abstraction instead of print directly to "system.out". For example:

 interface Output {
    void print(String data);
 }

Then you inject this dependency into the class that needs to send information to the output:

class MyProgram {

  private Output out;

  public MyProgram(Output output) {
     this.out = output;
  }

  public doSomething() {
     // do something
     out.print("i do something!);
  }

}

Then you can test easily with a mock (with mockito for example):

public void test_my_program() {

    Output mockOutput = mock(Output.class);
    MyProgram myProgram = new MyProgram(mockOutput);

    myProgram.doSomething();

    verity(mockOutput).print("do something!");
}

I don't verify the code but its more or less correct and i expect enough for you to get the idea. Always its the same, testing its not difficult, the difficult thing its design good testable code, here we are only using abstraction and dependency injection, two basic principles of OO.

The real advantage of this code its that now its not tied to "System.out", you can use this class in a web application for example if you want. For example making and output implementation that talks to the web client via websocket. This is another OO principle, your class is now "Open-Close", you can add functionality (websocket crazy example :P) without modify your actual code.

Reading System.out Java Test

3 Answers3