Home
Emmanuel Hugonnet's Library tagged → View Popular
MockFtpServer - Home
The MockFtpServer project provides a mock/dummy FTP server implementations that can be very useful for testing of FTP client code. Two FTP Server implementations are provided, each at a different level of abstraction.
Antonio Goncalves' Website - TestingJPA
This tutorial shows you how to run and unit test a simple JPA Entity with Eclipse Link, Maven, JUnit 4 and DbUnit. It uses MySQL 5 to run in production mode and Derby embedded for testing. This tutorial assumes that you are familiar with Maven, JPA and JUnit.
Multithreaded Testing at Carbon Five Community
Every now and then you’ll work on something that needs to handle requests from multiple concurrent threads in a special way. I say “special way” because in a web application, everything needs to handle being executed concurrently and there are a slew of techniques used to handle this (prototypes, thread locals, stateless services, etc). Here’s an example of what I mean by “special”…
OSGi based Integration testing with TestNG and Apache Felix [www.talios.com]
After thinking up various interesting, but overkill ways of OSGi-enabling TestNG to provide some nice integration testing I settled on the simplest approach (which also looks to be the best, and most flexible so far): embed felix - we already had a custom Felix launcher so this was very much similar (and so simple that it's almost not worth blogging about).
mrdon's maven-itblast-plugin at master — GitHub
Maven 2 plugin that runs integration tests on multiple servers
Functional testing with Maven, Cargo and Selenium
Setting up automated functional integration tests is not too hard if you have the right tools. It can take you a bit of time to setup but in the long run you'll benefit from reduced QA times, reduced risks, a more confident development team, the ability to do safe refactorings, and many more advantages.
I'm going to explain how Maven, Selenium, Cargo and JBoss 4.2 can be setup to run automatically in a continuous integration server such as Continuum customizing the server configuration as needed and deploying any webapp automatically. Every time the webapp is changed the CI server will execute the tests against the latest version ensuring you are always in a safe state.
The biggest difference with other tutorials I've found is that most of them cover just Jetty and are not updated to the latest versions of libraries and tools, so here it is my contribution.
robotframework - Google Code
Robot Framework is a Python-based keyword-driven test automation framework with an easy-to-use tabular syntax for creating test cases. Its testing capabilities can be extended by test libraries implemented either with Python or Java. Users can also create new keywords from existing ones using the same simple syntax that is used for creating test cases.
Features
* Enables easy-to-use tabular syntax for creating test cases in a uniform way.
* Provides ability to create reusable higher-level keywords from the existing keywords.
* Provides easy-to-read result reports and logs in HTML format.
* Is platform and application independent.
* Can natively use both Python and Java test code.
* Provides a simple library API for creating customized test libraries.
* Provides a command line interface and XML based outputs for integration into existing build infrastructure (continuous integration systems).
* Provides support for Selenium for web testing, Java GUI testing, running processes, Telnet, SSH, and so on.
* Supports creating data-driven tests.
* Provides tagging to categorize and select test cases to be executed.
Unit tests are not integration tests
The classic difference between integration and unit testing is that unit tests run in isolation, or near-isolation. Using an in-memory database for DAO unit tests. Using mocked-out components for the other layers. Integration tests, on the other hand, test the whole stack. If you're using Spring, you inject the whole Spring context and try to flush out any configuration issues, or integration issues between the various layers.
In pursuit of code quality: Don't be fooled by the coverage report
Test coverage tools bring valuable depth to unit testing, but they're often misused. This month, Andrew Glover brings his considerable expertise in this area to his new series, In pursuit of code quality. This first installment takes a closer look at what the numbers on the coverage report really mean, as well as what they don't. He then suggests three ways you can use your coverage to ensure code quality early and often.
JEXIN
Jexin is a web based functional testing/debugging platform for Java applications. The user can view details about the execution path (stack trace) in one or more JVM(s) and inject exceptions into the path to simulate faults. Jexin supports several views of stack traces including side-by-side comparison and merging of traces from different threads/JVMs into a single trace. Jexin does not run tests; it monitors the application and injects exceptions. The tests may be run manually or using a testing framework.
Blog Xebia France - Optimisez les performances de vos tests fonctionnels avec Selenium Grid
Nous ne rentrerons pas ici dans le détail de l'utilisation de Selenium (qui est très bien documenté sur le site officiel) hormis un exemple simple, mais nous regarderons plutôt comment paralléliser les tests avec Selenium Grid.
testability-explorer - Google Code
Testability-explorer is a tool which analyzes java byte-codes and computes how difficult it will be to write unit-test. It attempts to help you quantitatively determine how hard your code is to test and, where to focus to make it more testable.
Test metric tool can be used:
1. As a learning tool which flags causes of hard to test code with detailed breakdown of reasons.
2. To identify hard to test hair-balls in legacy code.
3. As part of your code analysis-toolset.
4. As a tool which can be added into continuous integration that can enforce testable code.
Automate Website Testing with Selenium RC
One of the difficulties I face when we do a release is regression testing - specifically testing the front-end (website) to ensure everything is working/looking correct. At the moment we have a team of 2 testers who work almost feverishly when a release is getting close to ensure that it is indeed a good release. To address this issue I have been looking at Selenium and how we can use it to automate a large portion of this regression testing.
InformIT: Exploratory Testing on Agile Teams > An Elusive Bug
Jonathan Kohl relates an intriguing experience with a slippery bug that convinced his team of the value of exploratory testing: simultaneous test design, execution, and learning.
InformIT: Conventional Software Testing on an Extreme Programming Team > Experience 1: Early Success
For a conventional software tester, an XP project may be an intimidating challenge. Testers often find that they're not welcome on XP projects, but the author shares how skilled testing can overcome such difficulties and discusses lessons he learned.
InformIT: Conventional Software Testing on a Scrum Team > What Is Scrum?
The Scrum methodology can pose a challenge for software testers who are used to more traditional waterfall-inspired development processes. The author relates his experiences working on Scrum teams who found some clear advantages in changing their methods.
TestLink Home
TestLink enables to create and manage Test cases as well as organize them into Test plans. These Test plans allow team members to execute Test cases and track results dynamically, generate reports, trace software requirements, prioritize and assign tasks.
mockito - Google Code
Java mocking is dominated by expect-run-verify libraries like EasyMock or jMock. Mockito offers simpler and more intuitive approach: you ask questions about interactions after execution. Using mockito, you can verify what you want.
Speedy unit testing with Jackrabbit
We're using Apache Jackrabbit for one of the JCR implementations in our unit tests.
So we've found that the easiest way to speed up Jackrabbit is to use the in-memory persistence manager and the in-memory file system implementations.
mock-javamail: Mock JavaMail - Mock JavaMail
Testing JavaMail applications is more difficult than necessary, because it involves in a lot of set up outside. Mock JavaMail takes advantage of pluggability in JavaMail, so that you can send/receive e-mails against the temporary in-memory "mailbox".
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in unit-test
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo