Scan this and find out more about the Arquillian project. http://arquillian.org Arquillian Overview Community Project So you rule your code. Not the bugs. Arquillian* is an open, innovative and extensible testing platform that enables developers to easily create automated integration, functional and acceptance tests for Java software. Testing is still the biggest challenge for developers building on the Java enterprise platform. Arquillian solves this problem in a radical way that not only makes testing possible, it gives tests real value. It even enables developers to take on scenarios previously considered untestable or too expensive to test. Picking up where unit tests leave oﬀ, Arquillian handles all the plumbing of container management, deployment and framework initialization so you can focus on the task at hand, writing your tests. Real tests. In short… Arquillian works by moving the code under test to the runtime so the test doesn’t need to embed or mock the runtime itself. Arquillian eliminates this burden by handling all aspects of test execution, which include: • Managing the lifecycle of one or more containers • Packaging the test case, dependent classes and resources into ShrinkWrap archives • Deploying the archives to the containers • Enriching the test case by providing dependency injection and other declarative services • Running the client and/or in-container tests • Capturing the results and transporting them to the test runner for reporting As soon as you begin integrating components inside a runtime, whether it be embedded or standalone, you need a service to manage that runtime. at’s Arquillian’s core concern. Arquillian puts the code to test inside the runtime and then delegates to extensions to help integrate components, invoke services, navigate web pages, measure performance characteristics, report code coverage and pass tests through the cloud, just to name a few. Arquillian provides a component model for tests, one that matches the programming model used to develop the application. e Arquillian project adheres to three core principles: 1. Tests should be portable to any supported container 2. Tests should be executable from both the IDE and the build tool 3. e platform should extend or integrate existing test frameworks By focusing on these principles, Arquillian makes integration and functional tests as simple to write and execute as unit tests. Find out more at http://arquillian.org No more mocks. No more container lifecycle and deployment hassles. Just real tests! * Arquillian has been tested against JBoss EAP, SOA-P, BRMS, EWS and EDS

Arquillian* is an open, innovative and extensible testing platform … · 2015-03-04 · Arquillian puts the code to test inside the runtime and ... one that matches the programming

Download PDF Report

Upload
others
View
7
Download
0

Embed Size (px)

Citation preview

Page 1: Arquillian* is an open, innovative and extensible testing platform … · 2015-03-04 · Arquillian puts the code to test inside the runtime and ... one that matches the programming

Scan this and find out more about the Arquillian project.http://arquillian.org

Arquillian OverviewCommunity Project

So you rule your code. Not the bugs.

Arquillian* is an open, innovative and extensible testing platform that enables developers to easily create automated integration, functional and acceptance tests for Java software.

Testing is still the biggest challenge for developers building on the Java enterprise platform. Arquillian solves this problem in a radical way that not only makes testing possible, it gives tests real value. It even enables developers to take on scenarios previously considered untestable or too expensive to test.

Picking up where unit tests leave o�, Arquillian handles all the plumbing of container management, deployment and framework initialization so you can focus on the task at hand, writing your tests. Real tests. In short…

Arquillian works by moving the code under test to the runtime so the test doesn’t need to embed or mock the runtime itself. Arquillian eliminates this burden by handling all aspects of test execution, which include:

• Managing the lifecycle of one or more containers• Packaging the test case, dependent classes and resources into ShrinkWrap archives• Deploying the archives to the containers• Enriching the test case by providing dependency injection and other declarative services• Running the client and/or in-container tests• Capturing the results and transporting them to the test runner for reporting

As soon as you begin integrating components inside a runtime, whether it be embedded or standalone, you need a service to manage that runtime. �at’s Arquillian’s core concern. Arquillian puts the code to test inside the runtime and then delegates to extensions to help integrate components, invoke services, navigate web pages, measure performance characteristics, report code coverage and pass tests through the cloud, just to name a few.

Arquillian provides a component model for tests, one that matches the programming model used to develop the application.

The Arquillian project adheres to three core principles:

1. Tests should be portable to any supported container2. Tests should be executable from both the IDE and the build tool3. �e platform should extend or integrate existing test frameworks

By focusing on these principles, Arquillian makes integration and functional tests as simple to write and execute as unit tests.

Find out more at http://arquillian.org

No more mocks. No more container lifecycle and deployment hassles. Just real tests!

* Arquillian has been tested against JBoss EAP, SOA-P, BRMS, EWS and EDS