BWUnit™ follows in the footsteps of other code-driven testing frameworks such as JUnit, borrowing key concepts including assertions and test fixtures and introduces them to the BusinessWorks™ development world. Effective unit testing with BWUnit™ allows your developers to isolate individual processes within your BusinessWorks™ projects to show they function correctly.
BWUnit™ lets you test the “units” of your team’s BusinessWorks™ projects, which other testing tools such as Parasoft® SOATest™ and eviware soapUI simply cannot reach. Running tests within the same memory space as your BusinessWorks™ project not only allows your team to test individual processes, it also enables your team to use mock objects such as in-memory databases and embedded JMS implementations, which makes it possible for them to test each process more thoroughly.
Unit testing alone with BWUnit™ does not form a comprehensive and complete testing strategy, which is why BWUnit™ provides a Web Service test execution API, allowing it to integrate easily with your existing SOA testing strategy and processes.
BWUnit™ is built to work out of the box with Continuous Integration servers, such as Hudson, CruiseControl and ThoughtWorks Cruise. It comes with the Apache Ant macros you'll need to build your design time libraries and run your tests. It even produces NUnit compatible test reports, so not only will your Continuous Integration server be able to tell you that a test failed, but which test and why. It's even smart enough to run your tests by launching the BusinessWorks™ engine directly, rather subjecting you to the overheads of building a testing EAR and deploying it to a TIBCO Administrator™ instance.
BWUnit™ has been designed with your developers in mind. Our team has commercial software development experience going back to 1999, unit testing experience going back to 2000 and has been in the TIBCO space since 2001. We know what BusinessWorks™ developers need from a unit testing framework and we know how to provide it in a way that is going to work for them, not against them.
Ask any BusinessWorks™ developer what the most painful thing about working on many projects is and one of their top answers will be "managing and maintaing file aliases". BWUnit™ introduces the unique Designer Launch Control, which opens projects in TIBCO Designer™ using file aliases and class path settings stored in the projects Apache Ant scripts. Designer Launch Control makes sure that every developer working on the same project is using the same file aliases.
BWUnit™ supports the key unit testing concepts of test suites, nested test suites, test cases, test fixtures, assertions, mock objects and of-course tests. If your developers have done any unit testing before, they will feel right at home with BWUnit™. If they have not, the large amount of unit testing material on the internet will help them get up to speed.
BWUnit™ tests are written in TIBCO Designer alongside the processes and services your team is developing. Using the same IDE for test development your team is currently using to build BusinessWorks™ projects results in a familiar test development environment, which is easier to learn and use. Having tests in the same development environment also means your developers can stay “in the zone” as they switch back and forth between writing services and writing tests for those services, increasing their productivity while keeping defect counts low.
BWUnit™ allows your developers to quickly switch back and forth between developing and testing, enabling them to quickly validate each component as it is added or changed. Keeping the develop-test cycle small allows your team to develop services and orchestration logic faster, increases their productivity and reduces their frustration.
Test fixtures, a key unit testing concept, makes it possible to set up the necessary data before the tests are run, so they always have the right data, without the need for manual test data preparation in between each run. Test fixtures also allow tests to clean up after themselves, returning the system to the state it was before the test was run. All this enables your developers to run any test at any time to get an up-to-date picture of the state of your BusinessWorks™ projects.
BWUnit™ provides a feature-rich, browser-based user interface for test execution, implemented using the award winning TIBCO General Interface™. The Test Execution UI is designed to show your developers the information they need to know: which tests passed, which tests failed and why they failed. A full process stack report and error data details will help your developers track down defects fast.
BWUnit™ gives your developers the control they need, allowing them to execute a single test, a test case, a test suite or all of the tests. This makes it possible for them to focus on a single failing test until it passes, They can then move up through the testing hierarchy, running more tests, ensuring their change has not broken anything else.
BWUnit™ uses a simple, customisable directory structure to organise your tests. Adding and removing tests simply involves creating and destroying processes. Adding and removing test cases and test suites simply involves creating and destroying folders. Simple.
That’s right, we eat our own food. If BWUnit™ wasn’t good enough for us, then we wouldn’t expect it to be good enough for you.
Join the Beta, Download BWUnit™ Now and find out what you're missing out on.