Skip to content

Software Development News: .NET, Java, PHP, Ruby, Agile, Databases, SOA, JavaScript, Open Source

Methods & Tools

Subscribe to Methods & Tools
if you are not afraid to read more than one page to be a smarter software developer, software tester or project manager!


The Latest Legal Developments in Open Source

Black Duck Software Press Releases - Fri, 05/09/2014 - 16:30

Open source software (OSS) has become a fundamental part of the IT infrastructure of virtually all companies. Such criticality naturally gives rise to legal issues as organizations protect their own interests in the context the sharing inherent with open source.

Recently there has been a shift from enforcement activity by non-profits to commercial entities with two lawsuits which enforce the GPLv2 being filed by commercial  companies in 2013. One of the lawsuits involves GPLv2 licensed code im a commercial product and has broader impacts for both commercial and open source  companies. Patent activity around open source has continued apace and contribution agreements are getting more attention as companies evolve from consuming open source to contribution back.

This webinar, presented by Black Duck with Karen Copenhaver, partner at Choate Hall & Stewart and Counsel for the Linux Foundation and Mark Radcliffe, partner at DLA Piper and General Counsel for the Open Source Initiative (OSI), will review:

  • The rise in importance of open source for commercial entities
  • Explain the lastest developments for OSS licenses, patents and contributor agreements.
  • What to look out for in the open source legal sphere during 2014.
Register Now
Categories: Vendor

A Guide to M&A Success

Black Duck Software Press Releases - Wed, 04/30/2014 - 16:30

Open source software is ubiquitous and widely used in development organizations to build better software faster. The day-to-day practice of using open source software is often uncontrolled, potentially creating unknown legal, business and operational risks arising from the often overlooked and misunderstood obligations found in many open source licenses.  As a result, acquiring companies are now focusing more heavily on open source and third party code in their due diligence practices to uncover issues before M&A transactions are completed.

Join this Webinar with Black Duck Software and Anthony Decicco, Partner at GTC Law Group and learn about the new industry norms with respect to open source due diligence.  

Attendees will learn:

  • The steps involved in the due diligence process
  • Possible impacts on a transaction, due diligence and definitive agreements   
  • Challenges and common concerns of acquirers and investors and ways to address these concerns well before a transaction
Register Now
Categories: Vendor

Appvance Adds JMeter Testing To PerformanceCloud

Appvance has announced the addition of JMeter compatibility in Appvance PerformanceCloud, its next generation cloud testing platform that combines functional, performance, stress, load tests and APM. JMeter is widely used by individual software p ...
Categories: Vendor

Targetprocess 3 Launches to Bring Visualization and Flexibility to Project Management

Targetprocess announced the availability of Targetprocess 3, which now includes more ways to visualize project data, track work across multiple teams and align business initiatives with development. This latest release reinforces Targetprocess&rs ...
Categories: Vendor

Upcoming European Training Courses Latest News - 2 hours 54 min ago
We are very pleased to remind you about our upcoming European Ranorex training courses, scheduled for June.

During the 2-day training workshops participants learn about the fundamentals of test automation and get to practice how to use Ranorex tools hands-on. 

Jun 2-3

09:00AM - 04:30PM GMT

Ranorex Studio Introduction Training Course

London, UK

Jun 3-4

09:30AM - 05:00PM CET

Basisschulung – Test-Automatisierung mit Ranorex

Frankfurt, Germany

Please have a look at the upcoming training events schedule for the complete schedule.

We look forward to seeing you there!

Categories: Vendor


Software Development Tools Directory - Wed, 04/16/2014 - 16:22
redmine_task_board is a Redmine plugin which creates Kanban-style drag and drop taskboards per project.
Categories: Vendor


Software Development Tools Directory - Wed, 04/16/2014 - 16:20
Gillie is a lightweight MVC framework inspired in Backbone. It provides useful methods to perform RESTful HTTP requests and allows for a separation of concerns using models, views and handlers. On the other hand offers an events API with which yo ...
Categories: Vendor


Software Development Tools Directory - Wed, 04/16/2014 - 16:18
Pylot is a free open source tool for testing performance and scalability of web services. It runs HTTP load tests, which are useful for capacity planning, benchmarking, analysis, and system tuning. Pylot generates concurrent load (HTTP Requests) ...
Categories: Vendor

Nevron announces the immediate availability of Nevron Vision for .NET 2014.1!

Software Development Tools Directory - Wed, 04/16/2014 - 14:33
Wilmington, Delaware — April 14, 2014 — Nevron Software is proud to announce the immediate availability of Nevron Vision for .NET 2014.1 : the award winning suite of data visualization controls for Server and Desktop .NET application ...
Categories: Vendor

ROI elements of requirements management tools

Intland Blog - Wed, 04/16/2014 - 14:28
Categories: Vendor

Make your Ranorex Report fully comprehensible for Jenkins by using xUnit Latest News - Tue, 04/15/2014 - 15:53

A Ranorex test automation project creates an executable file which returns a two-state test result indicating a success or a failure. Continuous Integration (CI) tools like Jenkins, Hudson, TeamCity, CruiseControl, Bamboo etc. are able to call automated tests and do understand these two-state test results. This is similar with ALM tools like Polarion or Jira. In short, in the world of CI and ALM, test automation results are reflected by a single flag, success or failure.

This blog describes how a Ranorex Report can be automatically transformed into xUnit format by using an XSL Transformation (XSLT). This transformation allows the CI tool to fully understand the result of each test case, not only whether the entire test run passed or failed.

The following example shows how UI test results can be interpreted following the same standards as xUnit tests do. Furthermore an example implementation of an XSL transformation file can be downloaded at the end of this blog.


The blog post “Integrating Ranorex Automation in Jenkins CI Process” is introducing the entire CI topic and gives a step by step introduction on how to integrate Ranorex into Jenkins CI. On the top of that, optimizations can be done supporting the machined understanding of the Ranorex Report.

Nowadays most of the modern unit testing frameworks such as JUnit, NUnit etc. do implement the xUnit notation (list of implementations). This comes with the advantage that tests and their results are defined once following the xUnit standard, and can then be interpreted and understood independent from the respective target language (such as Java, C#, etc.). In addition, continuous integration servers like Jenkins do use xUnit to interpret the results of a test in a unified way. Although Ranorex is a UI testing and not a unit testing framework, there still is a way to also interpret the Ranorex test results (Ranorex Reports) in the same way as you might be used to from your (automated) unit tests.

Install xUnit Plugin for Jenkins

First, the xUnit-plugin needs to be installed on Jenkins. Therefore please navigate to “Manage Jenkins” in the main menu and click the “Manage Plugins” menu item.

The tab sheet “Available” now provides the possibility to install the “xUnit plugin”.

Please proceed by installing the plugin.

Activate Custom Transformation (XSLT)

Next, the transformation of the Ranorex Report to a xUnit-based report format has to be activated. Therefore navigate to your Ranorex project and bring up the project configuration.

Start by adding a “post build action” called “Publish xUnit test result report”.

Two new panels appear allowing to define the thresholds for failed and skipped tests (both, total and new). More importantly click the “Custom Tool” menu item in the drop down:

The file name of the Ranorex Report needs to be defined in the setting “Custom Tool Pattern”:

Please make sure that path and file name of your report file pattern match the definition of your build step that calls the Ranorex executable. Here is the one used by this example:

TestCIProject.exe /rf:Report-Build-%BUILD_NUMBER%

Note: The Ranorex command line argument “rf” (reportfile) allows defining the report file name including the extension. If no file-extension is provided, the default extension “rxlog“ will be used for the report frame file. Additionally, the XML file containing the relevant data will be created with a file-extension “” then. For details on all command line arguments please refer to the user guide, chapter Running Tests via Command Line.

Note also: The above used placeholders %BUILD_NUMBER% and ${BUILD_NUMBER} are provided by Jenkins. At the beginning of a test run they will be replaced automatically by the current build number. Please take care to use these notations correctly.

Another relevant setting is the path to the transformation file (XSLT). A sample file is shared on GitHub and can be downloaded here:

Given these settings, right after every Ranorex test execution triggered by Jenkins the Ranorex Report is automatically transformed into a xUnit-based XML file. This allows a deeper integration of test results into CI which will be described in the next section.

Exploring Test Results

Having applied the mentioned settings to your Ranorex project on Jenkins, a section “Test Result” will appear for every new test run.

Following the “Test Result” link, an overview site is presented providing useful information like “All Failed Tests” including their duration and age (since how many builds does test fail). Additionally, a short summary of all passed, skipped and failed tests is presented.

By clicking the plus icon of a failed test Jenkins presents error details and the stack trace additionally:

Also, Jenkins can now distinguish on the test case level whether a test case passed or failed. Before the conversion to xUnit format, Jenkins was only able to interpret the entire test result.


Calling your Ranorex test automation project from a Continuous Integration (CI) environment provides a lot of benefits and allows you to represent the results of the entire build process over time. However, even more information of every single test run can be gathered out when the Ranorex Report is fully understood by the CI tool. This understanding can be achieved by a transforming the test report into xUnit format. As visible above, there are only a few steps needed to see the results of every single test case instead of only one result of the entire test run. Furthermore these test case detail results can be used easier for further processing.

Although the sample above is using Jenkins as a CI tool this approach is the same for all CI tools understanding xUnit.

Further Reading


Categories: Vendor

Embarcadero Launches RAD Studio XE6

Software Development Tools Directory - Tue, 04/15/2014 - 15:14
Embarcadero Technologies, a provider of software solutions for application and database development, today launched Embarcadero® RAD Studio XE6, the complete multi-device, natively compiled app development platform for Windows, Android, iOS a ...
Categories: Vendor

StrongLoop Releases StrongOps 2.0 DevOps Service for Node.js

Software Development Tools Directory - Tue, 04/15/2014 - 15:10
StrongLoop has announced the general availability of StrongOps 2.0, the first Node.js specific application lifecycle management (ALM) solution to include both monitoring and DevOps capabilities for Linux, Windows and Mac. Node.js continues to gai ...
Categories: Vendor

Chef and Rackspace Collaborate to Expand Reach of Enterprise Chef

Software Development Tools Directory - Tue, 04/15/2014 - 14:59
Chef, the leader in IT automation, today announced that Rackspace, the open cloud company, is using Enterprise Chef for its DevOps Service. Rackspace DevOps Automation Service helps developers and IT operations teams automate the scaling of hybri ...
Categories: Vendor

WANdisco Releases SmartSVN 8.5

Software Development Tools Directory - Tue, 04/15/2014 - 14:51
WANdisco, a provider of high-availability software for global enterprises to meet the challenges of Big Data and distributed software development, today announced SmartSVN 8.5, the latest version of its platform independent graphical client for A ...
Categories: Vendor

Neotys Announces Neotys Team Server 2.0 for Collaboration and Concurrent Testing

Software Development Tools Directory - Tue, 04/15/2014 - 14:37
Neotys has announced Neotys Team Server 2.0, a central web-based server used to collaborate on test projects and test multiple applications concurrently.
Categories: Vendor

Ranorex 5.0.2 Released Latest News - Tue, 04/15/2014 - 09:00
We are proud to announce that Ranorex 5.0.2 is now available for download. General changes/Features
  • Added support for Firefox 29
  • Added "durationms" field to report activity XML nodes and a "timestampiso" (ISO8601) timestamp field to the report root activity XML node
Please check out the release notes for more details about the changes in this release.

Download Ranorex version here.
(You can find a direct download link for the latest Ranorex version on the Ranorex Studio start page.)

Categories: Vendor

Resource Article on Covering IIS and Web Apps

Covering IIS and Web AppsCollecting code coverage on your web apps is crucial as part of both the development and QA process for any .NET team.  NCover’s approach for collecting code coverage allows you to perform both automated and manual tests and aggregate that collection regardless of how you like to test your web apps.  The key to this approach is setting up a project and using pre-coverage filters.

Specifically, NCover watches the w3wp.exe, the IIS worker process, in order to collect coverage. This approach allows you to automatically capture coverage once you have properly configured your project.

If this is your first time covering IIS with NCover, you may find the “auto-configure” method the easiest.  If you are experienced, you may prefer the manual approach.

The three-step process for covering IIS with NCover can be found at

If you have any questions with getting setup, please feel free to contact technical support.

The post Resource Article on Covering IIS and Web Apps appeared first on NCover.

Categories: Vendor

Welcome to Morris Medical Monday

Polarion Software - Mon, 04/14/2014 - 11:00
First of a new series "Morris Medical Monday" by Polarion consultant Daniel Morris. Each Monday medical device other medical related companies will get useful information about using Polarion and Polarion extensions to streamline development, make compliance easier, and accelerate time to market.
Categories: Vendor

Featured Extension: Polarion Work Item Integration with Tortoise SVN

Polarion Software - Fri, 04/11/2014 - 17:41
Featured Extension Polarion4Tortoise boosts developer productivity by integration Polarion with the Tortoise SVN client.
Categories: Vendor