Continuous Integration Server with Functional UI test execution in parallel

Version 1.0.7

All Platforms


BuildWise FAQ

BuildWise is an easy-to-use Continuous Integration Server. As we all know, CI's importance is increasingly getting realized (Google CEO checks Android CI server build status everyday). Without automated testing, especially fully end-to-end UI testing, a build is not a trustable build. And the same time, UI test execution is long (if you have this issue, Congratulations! You actually can develop and maintain a large number of test scripts), a continuous build server can help that.

BuildWise is designed to be simple and have good integration with UI testing.

BuildWise (still under development, its early access version) is free, available to

BuildWise works well with test scripts written in RSpec (and with TestWise integration).

BuildWise supports build commands that can be invoked from command line, i.e, common ones such as Ant, Rake and MSBuild work fine.

Windows, Mac OS X and Linux.

Yes. BuildWise even goes further with Dynamic Build Process, providing users very quick feedback on test executions. BuildWise Agent is required for distributed test execution.

What you described is typical, just as Martin Fowler said in his classic CI paper. But it can be started simple (then gradually adding more integration steps), especially setting up a continuous testing server for automated functional tests. Check out our screencasts, it can be done in minutes.

BuildWise is free and open-source, you can verify the license after download it, :-)

We are tired of hearing people talking about Agile, Test Automation and CI rather than spending real time doing it. We just simply don't want BuildWise be a part of these "empty talks". Without automated tests, there is little value using BuildWise anyway. So if you can do test automation and want to use BuildWise, just send us 20+ your automated test scripts, we will email you the download link.

Why 20 automated tests? We think 20 is a magic number, after done that, testers may get a sense of developing (and maintaining) a large number of tests (which is different from several demo ones). Also by then, testers get a real needs for using CI to manage test executions, which can help to master CI.

As BuildWise is free and open-source, we only offer technical support and CI coaching to our customers with 'Wise Support' package.

If our understanding of 'Cloud Testing' like yours, BuildWise has the capability. But we are yet to be convinced of 'Cloud Testing' except seeing hello-world alike examples. In reality, most organizations we know of are not comfortable in running their app in public domain for testing.

Functional testing execution is fragile, an unexpected popup window could just enough ruin the test execution. Also more importantly, putting it on cloud may not necessarily result in quicker feedback. For example, our sample web app has built-in database reset feature, which is of great value of all team members, especially testing. With database reset, we cannot run tests in parallel against single server instance. The right solution is to deploy the application to each machine where the agent is running. With BuildWise Agent installed on machines in your LAN, you have much better control.

Not really. In term of cost: hardware nowadays is quite cheap, US$500 can get you a decent machine without monitor. BuildWise is free and BuildAgent is only $199 each. Unless you are building next FaceBook or Twitter, the chance of your test execution time is in matter of hours, which is very admirable. 4 agents can reduce 2 hours test execution time to around 35 minutes.

In terms of effort, setting up BuildWise is simple and quick, so is the BuildWise Agent. Of course, like any CI solution, it depends on nature of your application.

Finally, once your build farm is set up, it can be easily configured to support another project, the resource is fully reusable.