bwunit-450x169

Compare Features

Features Lite Pro, Team and Enterprise Description
Core
Automated Acceptance Testing Yes Yes Tests can be written in a BDD style approach, with test steps shared between numerous tests
Integration Testing Yes Yes BWUnit can be used for multi-platform integration testing of any set of systems BW can integrate with
System Testing Yes Yes BWUnit can be used for multi-platform system testing for any system BW can integrate with
Unit Testing Yes Yes BWUnit can be used for unit testing BW projects
Load Testing Yes BWUnit tests can be executed by common load testing tools such as Apache JMeter, HP Load Runner
Multi-step Tests Yes Yes Multiple activities including sub-processes can be used with a single test allowing you to create complex test scenarios
Test Set-up and Tear-down Yes Fixtures can be used to set up and tear down test data for your tests
Stubs
Transport Stubs Yes Yes Transport Layer Stubs can be implemented as starter processes using the same shared resources as your feature code
Dependency Injection Yes Yes Activities that interact with dependencies can be encapsulated in processes, allowing you to use Dynamic Process Overrides to switch the implementation used during testing
In-memory DBs Yes Yes In-memory databases can be used during testing to avoid the need for production-like databases to be running or available from the test machine
In-memory JMS Yes Yes In-memory JMS implementations can be used during testing to avoid the need for production-like JMS implementations to be running or available from the test machine
Test Execution
CLI Execution Yes The full test suite can be executed from the command line via Apache Ant
CLI Partial Execution Yes A configured subset of tests can be executed from the command line via Apache Ant
Dynamic Partial Execution (UI) Yes Users can dynamically select test subsets or individual tests to execute from the BWUnit UI
Dynamic Partial Execution (Designer) Yes Yes Users can select individual tests to execute from the BWUnit from directly within TIBCO Designer
Scheduled Execution Yes Test runs can be scheduled using common CI servers, such as Jenkins, Hudson and Bamboo
Execution on Code Commit Yes Test runs can be triggered to run after a code commit using common CI servers, such as Jenkins, Hudson and Bamboo
Data-driven Testing
Recording and Baselining Yes Yes Tests can be written to record responses to a file or database and compare them to a previous baseline
Bulk Load Yes Yes Tests can be written to bulk load requests from a file or database
Test Parameterisation Yes Yes Common test steps can be refactored into parameterised sub-processes and used across multiple tests
Reporting
Machine-readable Reports Yes Machine-readable test results are recorded in JUnit compatible XML format
Human-readable Reports Yes Human-readable test results are recorded in HTML format
Coverage Reports Yes BW code coverage reports are recorded in Emma compatible XML format
Report Archiving Yes Test reports can be archived using common CI servers, such as Jenkins, Hudson and Bamboo or uploaded in code quality tools such as Sonar or published to a central repository, such as Nexus, Artifactory or even SharePoint
Configuration
Shared Environment Configuration Yes Yes Global Variables for each environment can be stored in properties files and used for both test runs and deployments
Shared Schemas and WSDLs Yes Yes BWUnit tests use the same XSDs and WSDLs as your feature code
Shared Connection Resources Yes Yes BWUnit tests use the same RV, JMS, HTTP and JDBC connection resources as your feature code
Transports
SOAP/HTTP(S) Yes Yes BWUnit tests can interact with SOAP/HTTP(S) Web Services using any of the BW SOAP activities
SOAP/JMS Yes Yes BWUnit tests can interact with SOAP/JMS Web Services using any of the BW SOAP activities
HTTP(S) Yes Yes BWUnit tests can interact with HTTP(S) interfaces using any of the BW HTTP activities
TIBCO Rendezvous Yes Yes BWUnit tests can send and receive RV message using any of the BW RV activities
TIBCO EMS Yes Yes BWUnit tests can send and receive EMS message using any of the BW JMS activities
IBM WebSphere MQ Yes Yes BWUnit tests can send and receive MQ messages using any of the BW JMS activities or using MQ Adapter and the corresponding Adapter activities.
JDBC Yes Yes BWUnit tests can interact with databases using any of the BW JDBC Activities
FTP Yes Yes BWUnit tests can interact with FTP servers using any of the BW FTP activities
TCP Yes Yes BWUnit tests can send and receive raw TCP using the BW TCP activities
TIBCO Adapters Yes Yes BWUnit tests can interact with TIBCO adapters using any of the BW adapter activities
Tool Integration
CI Servers Yes BWUnit tests can be executed from common CI servers such as CruiseControl, Jenkins, Hudson, Bamboo, TeamCity and Go
Artifact Repositories Yes Test reports can be published to common artifact repositories such as Artifactory and Nexus
Code Quality Management Yes Test reports can be uploaded to code quality management tools such as Sonar
Software Delivery Techniques
Test-driven Development Yes Yes BWUnit can be used for test-driven development of your BW projects
Behaviour-driven Development Yes Yes BWUnit tests can be written using BDD’s “Given, When, Then” style, with each test step implemented as a sub-process
Continuous Delivery Yes Yes The automated testing BWUnit allows is an essential part of any continuous delivery pipeline