Group items matching

in title, tags, annotations or url

"Units of Measurement API specifies one or more JavaTM packages for the programmatic handling of physical quantities and their expression as numbers of Units."

As Eclipse plug-in and Rich Client Platform developers, we face unique challenges in how we structure and execute our unit tests. In this article, I suggest an approach to unit testing based on Eclipse fragments that can help us overcome these challenges. If you find yourself frustrated with your current plug-in testing options, read on! But before going into detail on a fragment based solution, let's examine the current approaches and the pros and cons associated with each. The first approach is the one most of us start with as we learn the ropes of plug-in development: placing all code in a single plug-in.

Quick guide on where to use Assertion in Java with code example. Assertion in java is fairly underused feature but if used carefully can complement both Unit Testing and Exception handling. Since Assertion sits on code its gets more expose than Unit testing and can test your function with more real data than one or two test data.

"Implementation of Units of Measurement services. A coordinates module compliant with OGC/ISO specifications for the development and deployment of geographic applications. A rigourous mapping of mathematical structures (e.g. Group, Ring, Field, VectorSpace ) to Java interfaces. A linear algebra module, which includes a first (and I believe unique) parameterized matrix class capable of resolving linear system of equations involving any kind of elements (e.g. Complex, ModuloInteger, RationalFunctions) A functions module for symbolic calculations and analysis. Different types of numbers such as real numbers of arbitrary and guaranteed precision, or the always exact rational numbers. Support for exact or arbitrary precision measurements (also strongly typed). Support for Standard , Relativistic , High-Energy , Quantum and Natural physical models. A monetary module for precision-guaranteed calculations and currencies conversions."

"Unfortunately, in a distributed world, SOA or otherwise, it is rarely a good idea to use atomic short lived transactions (see the Cross-Service Transactions anti-pattern in chapter 10 for more details). Indeed, the fact that cross service transactions are discourages is one of the main reasons we would to consider using the Saga pattern in the first place. One of the obvious shortcomings of Sagas is that you cannot perform rollbacks. The two conditions mentioned above, locking and isolation do not hold anymore so you cannot provide the needed guarantee. Still, since interactions, and especially long running ones, can fail or be canceled Sagas offer the notion of Compensations. Compensations are cool; we can't have rollbacks so instead we will reverse the interaction's operation and have a pseudo rollback. If we added one hundred (dollars/units/whatnot) during the original activity we'll just subtract the same 100 in the compensation. Easy, right?"

"Assembla workspaces to accelerate software teams Ticketing and issue management, Subversion, Git, Mercurial, Wiki, and other collaboration tools to accelerate development. Unite your team with a single activity stream view. Free starter offers include free subversion, free git, standup/scrum reporting, and unlimited free services for public commUnities and open source projects. "

"JMockit allows developers to write unit/integration tests without the testability issues typically found with other mocking APIs. Tests can easily be written that will mock final classes, static methods, constructors, and so on. There are no limitations. The JMockit mocking API is simple, consistent, and minimal. There are no special methods or annotations that need to be used in test code, apart from those that really make sense. In general, the use of JMockit APIs for mocking leads to test code that is better structured and more readable. "

Encapsulation is a process of wrapping code and data together into a single unit. It is a way to achieve data hiding.

"Test in-container! Arquillian logo This space contains the user discussions and articles for the Arquillian project. The development discussions and articles are found in the Arquillian Development Space and the FAQs are located in the Arquillian FAQ Space. Information about the project can be found on the Project Site. We invite you to join us in the #jbosstesting channel on freenode IRC to chat about Arquillian, ShrinkWrap, Embedded AS and testing. This channel is logged by echelog and JBossBot is there to expand JIRA issues."

Arquillian enables you to test your business logic in a remote or embedded container. Alternatively, it can deploy an archive to the container so the test can interact as a remote client. The mission of the Arquillian project is to provide a simple test harness that abstracts away all container lifecycle and deployment from the test logic so developers can easily produce a broad range of integration tests for their enterprise Java applications. Arquillian is part of the JBoss Testing initiative, an umbrella project focused on providing a comprehensive testing tool set for application developers. Arquillian can either execute a test case inside the container, in which case the test class is deployed by Arquillian along with the code under test, or hold back the test class so it can act as a remote client to the deployed code. All the developer has to do is write the test logic. In short... Arquillian makes integration testing a breeze!