Creating and Running StreamBase JUnit Tests

A StreamBase JUnit test is a Java file based on the org.junit and com.streambase.sb.unittest packages. To use the StreamBase JUnit test feature, you must be able to write Java code, and you should be familiar with Java JUnit in general. Use the StreamBase JUnit feature with the following steps:

See StreamBase JUnit Test Tutorial for a step by step tutorial that walks through each step of generating a StreamBase JUnit test for one of the StreamBase samples.

When you create a new StreamBase project using the New StreamBase Project wizard, Studio offers the option to include the StreamBase Test Library to the new project's Java Build Path.

For existing projects, you must add both the JUnit 4 Library and StreamBase Test Library to the project's Java Build Path for your JUnit test code to be generated without errors. You can do this:

To create a new StreamBase JUnit Test:

The generated Java test file is a starting point only, with incomplete sections. You must customize the file by adding the exact tuple content you want to send to the module's input streams, and the exact tuple content you expect to see on the module's output streams. See Editing StreamBase JUnit Tests for a discussing of the required and optional edits for your JUnit test file.

package com.sb.support.test;

import com.streambase.sb.unittest.SBServerManager;
import com.streambase.sb.unittest.ServerManagerFactory;

public class baseMainTest {

  private static SBServerManager server;

  @BeforeClass
  public static void setupServer() throws Exception {
    // create a StreamBase server and load applications once for all tests in this class
    server = ServerManagerFactory.getEmbeddedServer();
    server.startServer();
    server.loadApp("main.sbapp");
  }

  @BeforeClass
  public static void setupServer() throws Exception {
    // create a StreamBase server and load applications once for all tests in this class

    // Set NowImplementation to IMPL_TIME_SERVICE instead of the default
    BaseTestEnvironment.DEFAULT_ENVIRONMENT.setNowImpl(NowImplementation.IMPL_TIME_SERVICE);

    server = ServerManagerFactory.getEmbeddedServer();

    // Create a ControllableTimeService to use as the server's time service
    timeService = TimeServiceFactory.getControllableTimeService();
    server.setTimeService(timeService);

    server.startServer();
    server.loadApp("main.sbapp");
  }

timeService.advanceTo(System.currentTimeMillis());

timeService.advanceBy(15, TimeUnit.SECONDS);

Run a StreamBase JUnit test like any other Java code in Studio: with the StreamBase JUnit test file selected, click the black triangle to the right of the Run button in the Studio tool bar. Select Run as → StreamBase Unit Test. You can also open the Run Configurations dialog to create and edit a launch configuration for your test file.

The StreamBase JUnit mechanism performs the following actions:

Success or failure is shown in the JUnit view, which shares the bottom pane of the SB Authoring perspective. A successful run shows with a long green bar and statistics, like the following example:

A failing run shows a stack trace that includes the tuples that failed to match the expected output:

Use the sbunit command to run a StreamBase JUnit test class at the command prompt. To use the sbunit command, you must have:

The minimum server configuration file for running sbunit is like this example:

<?xml version="1.0"?>
<streambase-configuration>
  <java-vm>
    <dir path="./java-bin" />
  </java-vm>
</streambase-configuration>

Run the test at the command prompt with a command like the following:

sbunit -f sbd.sbconf com.example.sbjunit.TestName

For information on the sbunit command, see sbunit.

If you specified a StreamBase deployment file in the Application under test field in the test-generating wizard, the generated JUnit test file includes a loadDeploy() line (instead of loadApp()), like the following example:

server.loadDeploy("deployFileName.sbdeploy");

The specified deployment file must have an <application> element with module and container attributes. The deployment file can also specify container connections, module parameters, and extension point external modules, as required.

The following deployment file example shows the minimum configuration that can be run with StreamBase JUnit:

<?xml version="1.0" encoding="UTF-8"?>
<deploy xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  xsi:noNamespaceSchemaLocation="http://www.streambase.com/schemas/sbdeploy/">
<runtime>
  <application container="default" module="BestBidsAsks.sbapp"/>
</runtime>
</deploy>

Back to Top ^