In the context of Java EE 6, unit tests are nice but worthless. Unit and integration tests execute chunks of the business logic in a single thread. Back-end resources and shared states are simulated with mocks. After the initial deployment, your application will never be executed again in a single thread. Strangely enough, most applications aren't load-tested until shortly before the deadline and are put into production regardless of the results. This session shows how to continuously stress-test your Java EE applications with open source tools and lots of fun!
02 outubro 2013
Stress-Testing Java EE 6 Applications Without Stress
About movie:
In the context of Java EE 6, unit tests are nice but worthless. Unit and integration tests execute chunks of the business logic in a single thread. Back-end resources and shared states are simulated with mocks. After the initial deployment, your application will never be executed again in a single thread. Strangely enough, most applications aren't load-tested until shortly before the deadline and are put into production regardless of the results. This session shows how to continuously stress-test your Java EE applications with open source tools and lots of fun!
In the context of Java EE 6, unit tests are nice but worthless. Unit and integration tests execute chunks of the business logic in a single thread. Back-end resources and shared states are simulated with mocks. After the initial deployment, your application will never be executed again in a single thread. Strangely enough, most applications aren't load-tested until shortly before the deadline and are put into production regardless of the results. This session shows how to continuously stress-test your Java EE applications with open source tools and lots of fun!
Subscrever:
Enviar feedback (Atom)
Sem comentários:
Enviar um comentário