#arquillian

[table42dot]

[sometimesgabby]

When you realize that Rick and Morty stole the idea of the “micro-verse battery” from Men In Black’s Arquillian Galaxy energy source... 

[bruno-bat]

Testes de Integração com Arquillian

No passado dia 16 de Abril tive o gosto de realizar esta apresentação junto do CoimbraJug. Aqui ficam os materiais para referência futura: -- Slides da Apresentacao (Google) -- Código fonte da demonstração (Github) A distinção entre testes unitários e de integração, as suas características e a importância de testar vários sistemas em conjunto serviram de introdução `a demonstração centrada no Arquillian, uma "framework" de testes de integração automáticos para aplicações empresariais construídas em Java. Foi explicada a arquitectura da ferramenta, como criar testes e executa-los em vários servidores. Foram descritos alguns problemas comuns das aplicações, que podem ser facilmente detectados com estes testes. Foi ainda abordada a configuração dos perfis Maven. Obrigado a todos os que apareceram.

[haru012]

[javaone2012]

Continuous Enterprise Development

"The purpose of automated testing is to enable change. Verifying correctness is just a nice side effect."

Types of Testing

When you write your own tests you get a sense of using your API. 

Acceptance tests - High level tests that match the business requirements.

Compatibility - Make sure that things work together.

Functional - Make sure stuff works.

Black box - test without knowing/thinking-about what's going on in the code.

White box - writing tests with the inside of code in mind.

Gray box - hybrid of black and white

Regression - Creating a test after finding a bug to make sure bug does not reappear.

Smoke - A huge sampling of data.

Load/Stress/Performance - Seeing how the system handles load.

Unit Test - Testing a single api call or some isolated code.

Integration Tests - Messy to do. You need a test harness, mocking, etc.

Continous Integration = Having a SCM, centralized build-system, continuous building (automated build system), and having a lot of tests (comprehensive test suite).

Continuous Development

Tests should be portable to any supported container.

Tests should be executable from both IDE and build tool.

The platform should extend/integrate existing test frameworks.

Arquillian - a component model for your testing.

Creates a deployment of an application for your test: @Deployment

You can use a yaml file with test data for your mock-database: @UsingDataSet("tesT_objects.yml")

Fragments within a page can be found and used in the test: @FindBy(id or xpath)

Warp.execute(ClientAction) to execute an action and verify the results.

Cloud

OpenShift, CloudBees

OpenShift with JBoss developer

.openshift/markers/ 

  java7 - use java7

  enable_jpda - enables remote debugging

Ability to runtime debug your openshift instance.

The book: Continuous Enterprise Development in Java

[webofdnw]

The galaxy is on Orion's belt.