Projects tagged ‘junit’ and ‘maven’

Web development framework written in java, based upon jdbc and Velocity. High test coverage, good object decomposition. Includes a shop, messageboards and CMS. Fully integrated with Maven 1 and 2.

Direct Democracy Portal, mixing open source with politics to create a portal for online organisations governed through direct democracy. Using maven, mysql, hibernate annotations (EJB 3.0), spring framework and ThinWire RIA Ajax Framework.

项目介绍：The Micrite is an application that developers can refer to when starting a web project base on Struts and Spring. It should aid you learn how to develop a complicated web application ... [More] , from coding to auto testing... Micrite是一个基于Struts和Spring的完整Web应用，通过它你会轻松的掌握： 如何设计开发一个的Web项目(面向对象设计,接口编程) 如何进行自动编译，测试及发布(Maven,ant,Junit) Struts2，Sping2，ajax等相关技术 项目特性： 基于maven的多模块Web应用，独立模块可以单独运行及发布 Struts2与Spring的完整实现 支持多种数据库, MySQL, Derby, PostgreSQL, Oracle, MSSQL extjs的完整实现, 独立模块动态加载 国际化支持 [Less]

We are looking for Javascript and jQuery developers to join our team to work on the Trump and the Engine sub-projects. Tellurium Automated Testing FrameworkThe Tellurium Automated Testing Framework ... [More] (Tellurium) is a UI module-based automated testing framework for web applications. The UI module is a collection of UI elements you group together. Usually, the UI module represents a composite UI object in the format of nested basic UI elements. For example, the Google search UI module can be expressed as follows, ui.Container(uid: "GoogleSearchModule", clocator: [tag: "td"], group: "true"){ InputBox(uid: "Input", clocator: [title: "Google Search"]) SubmitButton(uid: "Search", clocator: [name: "btnG", value: "Google Search"]) SubmitButton(uid: "ImFeelingLucky", clocator: [value: "I'm Feeling Lucky"]) }The UI module makes it possible to build UI elements' locators at run time. The framework does Object to Locator Mapping (OLM) automatically at run time so that you can define UI objects simply by their attributes, i.e., Composite Locators denoted by the "clocator". Furthermore, Tellurium uses the Group Locating Concept (GLC) to exploit information inside a collection of UI components to help finding their locators and the GLC is denoted by the "group" attribute in the above UI module. The Tellurium framework defines a new Domain Specific Language (DSL) for web testing. Still take the above Google search module as an example, you can use the following DSLs to do a Google search, type "GoogleSearchModule.Input", "Tellurium test" click "GoogleSearchModule.Search" waitForPageToLoad 30000One very powerful feature of Tellurium is that you can use UI templates to represent many identical UI elements or dynamic size of different UI elements at runtime, which are extremely useful to test dynamic web such as a data grid. One typical data grid example is as follows, ui.Table(uid: "table", clocator: [:]){ InputBox(uid: "row: 1, column: 1", clocator: [:]) Selector(uid: "row: *, column: 2", clocator: [:]) UrlLink(uid: "row: 3, column: *", clocator: [:]) TextBox(uid: "all", clocator: [:]) } Data Driven Testing is another important feature of Tellurium. You can define data format in an expressive way. In you data file, you can specify which test you want to run, the input parameters, and expected results. Tellurium automatically binds the input data to variables defined in your test script and run the tests you specified in the input file. The test results will be recorded by a test listener and output in different formats, for example, an XML file. Tellurium UI Model Plugin (TrUMP) is a Firefox plugin to automatically create UI modules for users. In addition, Tellurium provides you the capability to composite UI objects into a Tellurium widget object. You can pack Tellurium widgets as a jar file and then use a Tellurium widget just like a single tellurium UI object once you include the jar file. As a result, Tellurium is robust, expressive, flexible, and reusable. In summary, the main features of Tellurium include: Abstract UI objects to encapsulate web UI elements UI module for structured test code and re-usability DSL for UI definition, actions, and testing Composite Locator to use a set of attributes to describe a UI element Group locating to exploit information inside a collection of UI components Dynamically generate runtime locators to localize changes UI templates for dynamic web content XPath support jQuery selector support to improve test speed in IE Locator caching to improve speed Javascript event support Use Tellurium Firefox plugin, Trump, to automatically generate UI modules Dojo and ExtJS widget extensions Data driven test support Selenium Grid support JUnit and TestNG support Ant and Maven support The Tellurium Core is written in Groovy and Java. Tellurium Engine and Trump are implemented using JavaScript and jQuery. The test cases can be written in Java, Groovy, or pure DSL. You do not really need to know Groovy before you use it because the UI module definition and actions on UIs are written in DSLs and the rest could be written in Java syntax. Detailed User Guide, Frequent Asked Questions, and illustrative examples are provided. We expect and welcome your contributions. For a quick start, please read Ten Minutes To Tellurium, Ten Things You Should Know About Tellurium, and Top Ten Cool Features in Tellurium. Tellurium SubprojectsTellurium subprojects include Core, Reference projects, Widget extensions, TrUMP, and Engine projects as shown in the following diagram, Tellurium Engine: Based on Selenium Core with UI module, jQuery selector, command bundle, and exception hierarchy support. Tellurium Core: UI module, APIs, DSL, Object to Runtime Locator mapping, and test support. Tellurium Extensions: Dojo Javascript widgets and ExtJS Javascript widgets. Tellurium UI Module Plugin (TrUMP): A Firefox plugin to automatically generate the UI module after users select the UI elements from the web under testing. Tellurium Maven Archetypes: Maven archetypes to generate skeleton Tellurium JUnit and Tellurium TestNG projects using one Maven command. Tellurium Reference Projects: Use Tellurium project site as examples to illustrate how to use different features in Tellurium and how to create Tellurium test cases. How to use Tellurium ?There are three ways, i.e., use the reference project as a base, use Tellurium Maven archetype, or manually create Tellurium project using tellurium jar and Tellurium configuration file. Alternatively, you could create your own Tellurium Maven project manually using the sample POM file. Tellurium 0.7.0 core snapshots are at http://kungfuters.org/nexus/content/repositories/snapshots/tellurium/tellurium-core/0.7.0-SNAPSHOT/ Trump 0.2.0 snapshots are at http://kungfuters.org/nexus/content/repositories/snapshots/tellurium/TrUMP/0.2.0-SNAPSHOT/ Tellurium Maven RepositoryTellurium supports Maven 2 and here is the guide on how to use Maven for Tellurium. Tellurium snapshots can be found at our Maven snapshot repository and the releases are at our Maven release repository Tellurium provides two Maven archetypes, tellurium-junit-archetype and tellurium-testng-archetype for Tellurium JUnit and TestNG project, respectively. You can use one Maven command to create a new Tellurium test project. Tellurium SupportIf you have any questions or problems with Tellurium, please join our Tellurium user group and then post them there. You will get the response very shortly. AcknowledgmentsSpecial thanks to JetBrains for providing us the Open Source License for IntelliJ IDEA. Special thanks to ej-technologies for providing us the Open Source License for JProfiler. Special Thanks to AquaFold for providing us the Open Source Software Developer License of Aqua Data Studio. NEWS2009-10-10, Tellurium Facebook Group has been created and you are welcome to join. 2009-09-20, Special thanks to Davlyn Jones, the Tellurium user guide 0.6.0 is officially released now. 2009-09-18, Special thanks to Jared Rawlinson, Tellurium has a new project logo now. 2009-09-09, Please poll where did you find Tellurium. 2009-08-18, Welcome Kamal Ahmed to our team. 2009-08-15, Welcome Mahendra Kariya and Ajay Ravichandran to our team. 2009-07-27, The first draft of Tellurium User Guide is available now. You can download the pdf file from here. 2009-07-15, Welcome Kevin Zhang to our team. 2009-07-09, Welcome Davlyn Jones and Ramesh Ramamurthy to our team. 2009-06-26, Tellurium was presented at CodeStock 2009. 2009-06-26, Tellurium is on Twitter and Reddit now. 2009-06-24, Tellurium celebrates its first anniversary. Please read the article, Tellurium First Anniversary: Retrospect and Prospect. 2009-06-23, Added a video demo Tellurium beginner tutorial. 2009-06-21, Welcome Jeff Xiong to our Team. 2009-06-18, Tellurium 0.6.0 is released, please see the announcement. 2009-06-12, Tellurium creator, Dr. Jian Fang, was interviewed by InfoQ China. 2009-06-10, Tellurium Chinese Document project is created. 2009-05-13, Tellurium Core and reference projects 0.6.0 RC1 are out, Please see the announcement. 2009-05-10, Added Tellurium 0.6.0 feature introduction: Whats New in Tellurium 0.6.0 2009-04-28, Tellurium provides Selenium Grid support 2009-04-23, Tellurium Automated Testing Framework LinkedIn Group has been created and you are welcome to join. 2009-04-14, Tellurium starts to support jQuery selector. 2009-03-15, tutorial 10 Minutes to Tellurium is created and it includes a wiki page, presentation slides, and a screencast video. 2009-03-13, two Tellurium Maven archetypes are available, i.e., tellurium-junit-archetype and tellurium-testng-archetype for Tellurium JUnit and TestNG project, respectively. 2009-03-04, Tellurium UI Module Firefox Plugin (TrUMP) 0.1.0 is released 2009-02-18, Tellurium UI Module Firefox Plugin (TrUMP) 0.1.0 Release Candidate is available 2009-02-17, Tellurium Demo Videos are uploaded, you can use VLC media player to watch them 2009-01-29, Tellurium UI Module Firefox Plugin (TrUMP) 0.1.0 preview version is available 2008-12-03, Tellurium core 0.5.0 and reference projects are released 2008-12-02, Welcome Mikhail Koryak to our team. 2008-11-15, Tellurium 0.5.0 Release Candidate RC01 is out 2008-08-22, Welcome Haroon Rasheed to our team. 2008-08-13, Tellurium 0.4.0 is released and this release includes a lot of new features and enhancements such as data driven testing, framework configuration, and JUnit 4 support. 2008-07-29, The AOST framework is officially renamed to the Tellurium Automated Testing framework (Tellurium). 2008-07-29, Welcome Matt Senter to our team. 2008-07-18, Welcome Vivek Mongolu to our team. 2008-07-18, AOST user group is created. Please join and post your questions, comments, and suggestions there. 2008-07-12, AOST 0.3.0 is out and it comes with significant feature enhancement including Composite Locator, Group Locating Concept, and Multiple UI Modules in one DslContext. 2008-07-02, UI Object ID is refactored to support nested UI objects. 2008-06-25, The AOST framework became public with version 0.2.0. 2008-01-01, the AOST framework second prototype was created. 2007-06-01, the AOST framework first prototype was created. [Less]

Coverage of common approaches to building applications using the internet and relational databases as well as integrating these applications with other systems. Students will work in teams to build a ... [More] functional web application in a series of projects throughout the semester. Topics covered include transactions, object-relational mapping, model-view-controller architectures, web services, and asynchronous messaging. The course is designed around 4 programming assignments which are to be completed throughout the semester. Topics will be covered in a sequence which aligns with the due dates of the programming assignments. This course is an in-depth discussion of the challenges and complexities involved in designing and implementing modern distributed business applications. Students will gain experience designing and implementing a project during in the course of the semester. This process will give students experience with the following concepts: · Domain-driven design · Persistence techniques · Transactions · Component-based design · Service-oriented design · Model-View-Controller UI Frameworks · Web 2.0 concepts · System integration with HTTP, XML, Messaging, and Web Services · Agile development frameworks We will discuss these topics both from theoretical and practical perspectives. Throughout the course we will also discuss agile development best practices and have an opportunity to implement many as we complete projects. Discussions will focus on best practices highlighted with relevant, industry accepted approaches. The vast majority of frameworks and tools featured will come from best-of-breed open source projects. We will look at these projects not only to understand how they can be successfully used, but also critically on how they fail to address the core challenges of modern business application development. The programming assignments will be completed in two person teams. Each assignment will be focused on a core set of application development concepts (such as data, UI, integration, etc). Each assignment will require successful implementation of core requirements with functioning code and in some cases usable application. Requirements must be confirmed via unit tests to receive full credit. Assignments will be due and must be submitted via email to Instructor Calvo before midnight on the due date. The each submitted assignment must be an archive (zip) file of project source code, unit test, and build script which can be built and run on the instructor's computer. [Less]

J2me unit testingWhen using j2meunit, one has to manually enumerate and call the tests from inside the TestCase, as well as manually call all the TestCases from within a TestSuite. This is not only ... [More] tedious but one can also easily forget to add a test or make a mistake in the test name that can result in tests not being called. This tool generates a class that calls all test methods from all test cases in the project. This is completely automatic and is meant to be part of the build of the test midlet. This project aims to make unit testing for mobile devices as easy and robust as unit testing for the desktop. J2meunit generatorThe tool scans the given directory for all unit tests and generates a test suite that executes all the tests. The typical use is for the J2ME platform where there is no reflection support and without this tool one would have to enumerate all unit tests manually. Please take a look at the Example and don't hesitate to contact me in case of any questions or suggestions. Wojciech Mlynarczyk Using mavenAdd the following plugin to your pom file: ... com.googlecode.wmlynar j2meunit-generator-maven-plugin generate generate-sources com.googlecode.wmlynar.j2meunitgenerator.example.AllTests ${basedir}/src/main/java ${basedir}/src/main/java where testsDirectory is directory containing all the tests for example /src/testme/java, targetDirectory is the directory where the generated source code will reside for example also /src/testme/java, and the className is the name of the generated class for example pl.wmlynar.tests.AllTests Additional test suites can be generated by adding further testSuite blocks. Also add the plugin repository to the pom file: j2me-unit-testing http://j2me-unit-testing.googlecode.com/svn/mavenrepo Using the tool from the command lineThe tool can also be called from command line: java -jar j2meunit-generator-1.0-bin.jar --testsDir sdir --outputDir odir --generatedClassName namewhere similarly to maven plugin: sdir is directory containing all the tests for example /src/testme/java, odir is the directory where the generated source code should reside for example also /src/testme/java, and the name is the name of the generated class for example pl.wmlynar.tests.AllTests and the tool will generate a file /src/testme/java/pl/wmlynar/tests/AllTests.javaCalling from antJust use java ant task, for example: ExampleYou can take a look at the example provided with the source code. In order to compile the example you have to set the WTK_HOME environment variable pointing to the sun wireless toolkit. In my case it is: set WTK_HOME=c:\WTK2.5.2 [Less]

subfloor is a set of template Ant scripts that help you quickly stand up a complex Java project. The term "subfloor" comes from the construction industry. Merriam-Webster defines subfloor as "a ... [More] rough floor laid as a base for a finished floor". The idea behind the subfloor project is to support your "finished" build, in other words, subfloor will provide all of the functionality that a Java project needs in order to build, but let you "finish" your build by injecting custom behavior or overriding the the subfloor built-in tasks. In particular, subfloor provides many features to your build process out-of-box, such as: configurable javac compiling jar creation (with auto manifest population) source bundling javadoc creation and bundling JUnit testing and report generation Cobertura code coverage reporting Apache IVY dependency resolution, retrieval, and reporting automated version.properties file creation [Less]

一个java开发工程的演示：使用StarUML进行模式设计，maven构建工程，基于java实现，使用了junit进行单元测试。

Amongst other things tests proof that your code works the way you expect them to work. But how tests the tests? This Maven Plugin gives you some insight in the quality of your tests by counter the ... [More] number of asserts per test method. The plugin gives you a quick overview in the form of a Maven Report which tests have no asserts. [Less]

This project comprises a collection of maven plugins and other generic tools to help you perform common development tasks. jarinfoThe first available plugin is "jarinfo" which allows you you ... [More] generate information files containing the time your project's build took place and SVN information about the code it was built from. This can help when trying to differentiate between two different archives in deployment which have the same name but different sizes. how to use itThis plugin can be used by adding it's "jarinfo:gen-build-info" goal as a postgoal to the java:compile target and will create up to two files for you in your project's /src directory. The first file contains the timestamp of when the build took place. The second - which requires SVN to be installed on the build system - obtains the output of the "svn info" command run against the project's base directory. Each can be enabled or disabled by setting the relevant property. The produced info files can then be included in the project archive product by editing the tags in your project.xml file so that these are added to the archive. available properties and defaultsjarinfo.src.dir=src jarinfo.include.timestamp.info=true jarinfo.include.svn.info=falsepkgtestsThis is the second plugin. "pkgtests" takes your compiled project's code, tests, and dependencies and packages them all up as a zip file plus a .bat and .sh script to run the tests whereever you desire. Not immediately useful? The reason I wrote it was because we had a set of performance unit tests. We wanted to be able to run the tests not just on our local dev boxes, but also on the production systems. This allowed us to do this very simply. I am sure there are other uses. how to use itThis plugin can be used by calling it's "pkgtests:pkg" goal. The zipped tests etc will be placed in your target directory, in a file called "[your-project-name].zip". available properties and defaultspkgtests.suite.class.name=Set this in your project.properties fileThis needs to be set in your project's project.properties file and must refer to the JUnit test suite class (fully qualified - e.g. com.example.MyUnitTestSuite) If you like them, let me know. If you want changes or a have found a bug, let me know. If you want to help, let me know. Hope it helps. Look out for more to come. [Less]