ScalaCheck is a powerful tool for automatic unit testing of Scala and Java programs. It features automatic test case generation and minimization of failing test cases. ScalaCheck started out as a Scala port of the Haskell library QuickCheck, and has since evolved and been extended with features not found in Haskell QuickCheck.
EJBs in Scala schreiben
Was spricht eigentlich dagegen, eine EJB in Scala zu implementieren? Um diese Frage zu beantworten, habe ich ein Demo-Projekt aufgesetzt, in dem ich zwei EJBs in Scala implementiere.
Spde is an offshoot of the Processing environment to support sketches written in Scala, a powerfully object-oriented and functional language.
In contrast to the PDE, Spde is a deconstructed toolkit. For starters that means you bring your own editor and Spde will compile and run a sketch whenever you save it — that’s one option. The entire process is controlled by Scala code you can use or override. This structure should make Spde easy to extend and customize. But who knows, for now it is just a scrappy little thing with big ideas.
A tool for testing Scala and Java software
OSI Certified Open Source Software
ScalaTest is a free, open-source testing tool for Scala and Java programmers. It is written in Scala, and enables you to write tests in Scala to test either Scala or Java code. It is released under the Apache 2.0 open source license.
Because different developers take different approaches to creating software, no single approach to testing is a good fit for everyone. In light of this reality, ScalaTest is designed to facilitate different styles of testing. ScalaTest provides several traits that you can mix together into whatever combination makes you feel the most productive.
sbt is a simple build tool for Scala projects that aims to do the basics well. It requires Java 1.5 or later.
Features
* Fairly fast, unintrusive, and easy to set up for simple projects
* Configuration is done in Scala
* The default source directory layout is the same as maven's so you can always switch to maven should you need/want to
* Regardless of what sources you have added, changed, or removed, sbt should (in theory) recompile the right sources using information extracted from compilation with a compiler plugin
* Supports ScalaCheck, specs, and ScalaTest.
* Can generate documentation with scaladoc
* Packages jars (classes, sources, or api docs)
* Can start the Scala interpreter with the right classpath (dependencies and compiled classes)
* Multiple project/subproject support
* Parallel task execution, including parallel test execution
* Dependency management support: basic inline declarations, configuration with Maven (partial support) or Ivy, or manual management.
ScalaModules aims at Scala-based OSGi development. The mission of ScalaModules is to employ the power of the Scala programming language to ease OSGi development. Of course using Scala for OSGi will itself be beneficial, because of the great simplifications Scala brings compared to Java. But ScalaModules will also make use of the additional possibilities offered by Scala, mainly the chance to create a Domain Specific Language. Therefore with ScalaModules your code will be more intuitive and concise as well as less verbose and less involved compared to Java-based OSGi development.