BuildWise - AgileWay Demo

Edit project: Vibe Parallel Build RSpec Rails (vibe-parallel-build-rspec-rails) Duplicate User Stories

Test Execution Mode

Sequential Functional Parallel Functional Sequential Performance Parallel Load

Sequential (Functional and Performance): runs test scripts one by one on the build server machine;
Parallel Functional: distribute tests to BuildWise agents to run them in parallel to save time and increase reliability;
Load Testing: distribute tests to BuildWise agents to run them in parallel for load/performance testing purposes.

Source Control

Source Control

Authentication: Use Git Credential Manager, set up SSH keys or embed user:pass in .git/config.

Build Steps (only take effect after save, drag to sort execution order)

Build prepare command

UI Test

Test framework: Exclude suite name from test case:

Build cleanup command

UI tests (functional tests via GUI)

UI test folder *

The folder (relative path) contains the main UI test scripts, such as ui-tests/spec or features.

Parallel Test Execution (run tests on multiple BuildWise Agents)

Build Agents

Set specific build agents for this project. BuildWise will use all if not set.

Retry failed test files on another agent

Failed tests will be retried one more time on another Build Agent to reduce false alarms.

App name *

The name of application to be tested, the Application setting in BuildWise Agent shall match this.

Work directory on Agents *

The checked out or cloned top directory from repository, e.g.


          /Users/me/myproject

If you have agents on different platforms, separate them with ;

Distribution rules

Test Files	Rule	Agents	Active?

Environment Variables (pass to builder running on the server, not affecting build agents)

Current Environment Variables :

Add Environment Variable

Important: make sure BUILDWISE_MASTER URL correct and valid for lookup in server itself for distributed build. For Sequential Builds, the environment variables will be passed to test execution, common ones: BASE_URL, BROWSER.

Files/Directories to archive (relative to the project root dir, separate by ';')

Optional. The files listed here, if present, will be accessible on the build page after the build finishes.

User Interface (control features of BuildWise for this project)

Show test scripts to the public?

Syntax Highlight test output?

Use HighLight.JS to format code/scripts wrapped in <pre><code class='xml'> alike format. Warning: special tags in test output might conflict HTML causing BuildWise not showing correct, if that happens, turn this off.

Requirement Traceability Generate requirement traceability matrix from automated tests

External User Story URL Prefix

The link to external server (such as JIRA) for easier navigating to the user story. The story's external ID will be appended the above.

Deployment (on success builds, allow admin to invoke a Rake task to preform deployment)

Rake Task

Optional, the task name in Rakfile. An dropdown menu option is shown invoke this task for deployment.

API (configuration for the third party to interact with BuildWise server to manage builds of this project)

Project API Key

POST to /api/projects/vibe-parallel-build-rspec-rails/trigger_build?api_key=API_KEY. If the value is empty, API is not enabled.

Notifications (notify the build outcome)

Cancel