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!


Tech Tips & Tricks: Querying across Documents for unlinked Work Items

Polarion Software - Fri, 08/01/2014 - 17:28
More Tech Tips and Tricks from the Polarion Support Team. This time: Querying across Documents for unlinked Work Items
Categories: Vendor

Why Switch from SVN to GIT and DVCS?

Intland Blog - Fri, 08/01/2014 - 12:37
…and why the compromise in functionality is no longer necessary. There is a lack of understandable information on the benefits of GIT and Distributed Version Control (DVCS) over Version Control with Apache Subversion (SVN). While there are always those happy
Categories: Vendor

KronoDesk v1.1.0.10 Released

Inflectra News - Fri, 08/01/2014 - 01:00
We have just released the latest version of KronoDesk - v1.1.0.10 that includes several important fixes and well as some frequently requested enhancements.
Categories: Vendor

Case Study: Google’s Team Approach to Coverage

googleWe spend our days (and nights and really anytime we have) developing quality and beautiful .NET applications. We pour over our code, testing and coverage to make sure it is good. Some of us do that on our own while others are part of a larger network of teams with managers, developers and quality assurance members all along the way.

We all want to know that our code is good. We write tests to prove that and use coverage tools to show that we have strong tests. Rolling out a coverage process can feel pretty daunting whether you are in the same building or across the globe.

The team at Google recently gave us all a peek behind their curtain about implementing code coverage team-wide and its effects across the organization. (You can read the whole post here). We spliced it down into the Cliff’s Notes version with some key takeaways.

code-coverage-for-teamTheir team’s mission was to collect coverage related data and then develop and implement the code coverage practices company wide. To make it easy, they designed an opt-in system where engineers could enable two different types of coverage measurements for their projects: daily and per-commit. With daily coverage, Google ran all tests for their project, where as with per-commit coverage they ran only the tests affected by the commit. The two measurements are independent and many projects opted into both.

The feedback from Google engineers was overwhelmingly positive. The most loved feature they noted was surfacing the coverage information during code review time. This early surfacing of coverage had a statistically significant impact: their initial analysis suggests that it increased coverage by 10% (averaged across all commits).

Their process is ever-changing and growing. We will keep you posted on their activity along the way.

The post Case Study: Google’s Team Approach to Coverage appeared first on NCover.

Categories: Vendor

Ranorex 5.1.1 and Ranorex 5.0.4 released Latest News - Thu, 07/31/2014 - 09:40
We are proud to announce that Ranorex 5.1.1 and Ranorex 5.0.4 have been released and are now available for download.

Ranorex 5.1.1 General changes/Features
  • Added support for Firefox 31
  • Added support for ARM64 compiled iOS apps
  • Removed the requirement to link the MediaPlayerFramework for instrumenting iOS apps
  • Further improved mobile web elements to make attribute values similar to those of desktop web elements
  • Links shown in test case descriptions of a report are now opened in a separate browser window
Please check out the release notes for more details about the changes in this release.

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

Ranorex 5.0.4 General changes/Features 
  • Added support for Firefox 31
Ranorex 5.0.4 release notes...
Categories: Vendor

The Needs that Version Control Systems Serve

Intland Blog - Wed, 07/30/2014 - 17:02
Version control systems are divided into two groups: “centralized” and “distributed”. Centralized Version Control Systems (CVCSs) and Distributed Version Control Systems (DVCSs) serve different needs. Comparing Centralized Version Control Systems to Distributed Version Control Systems is like comparing hammers and
Categories: Vendor

Oracle Customers Plug into the Cloud with Oracle Database 12c

Oracle Database News - Wed, 07/30/2014 - 13:00
Oracle Customers Plug into the Cloud with Oracle Database 12c -- Latest version of world’s #1 database is available now, and includes new Oracle Database In-Memory technology to power the real-time /us/corporate/press/2252680 en
Categories: Database, Vendor

Enterprise vs. Developers: How Can ADLM Tool Vendors Conquer the Divide?

Polarion Software - Wed, 07/30/2014 - 07:00
There are two conflicting (or at least contradictory) viewpoints in the market for application development lifecycle management (ADLM) tools. There is enterprise management that needs to comply with regulations and so wants exert a high degree of control over development. There are developers who want to be self-organizing. Can vendors of ADLM tools bridge this […]
Categories: Vendor

Progress Enhances DataDirect Cloud with OData Connectivity

Progress Software News - Tue, 07/29/2014 - 14:00
Progress Enhances DataDirect Cloud with OData Connectivity
Categories: Vendor

Sharing Data from One Ranorex Module to Another Latest News - Tue, 07/29/2014 - 08:06

Sometimes it is necessary to access the value of a specific variable in more than only one module in a test case.

An example for this would be any kind of converter: In one module the value to be converted is read in. In another module this value is converted. Needless to say, in the converting module the value from the previous module should be used.

This blog post will show how to do this step-by-step.

The Structure of the Ranorex Solution

As you can see in the screenshot above, the solution “Converter” created for demonstration purposes consists of four different modules. Two variables (varTemperatureCelsius and varTemperatureFahrenheit) should be shared between the modules “GetValue” and “ConvertValue”. The temperatures are read from a weather-website in the “GetValue”-module.

In the “ConvertValue”-module the Celsius-temperature is converted from Celsius to Fahrenheit using another website and compared to the Fahrenheit-temperature from the first website. The whole example is available for download here.

Step 1: Creating a Variable in Module 1

At the beginning an “Open Browser”-action is recorded in the first module. Then a new “Get Value”-action in the second module “GetValue” is added.

Note: Before initializing a new variable, a repository item representing the UI element that displays the temperature needs to be created. This can be done by using the “Track”-button in the Ranorex Repository or by using the Ranorex Spy.

The value of the current temperature is stored in a variable. It is going to be created by clicking on the drop-down menu below the heading “Variable” and choosing the option “As new variable…”.

A context menu will be opened which should look like this:

Here the desired name of the variable and (optionally) a default value can be defined.

Note: The default value is used if modules are running separately and not from the test suite view. It will also be used if a variable is unbound and the test is started from the test suite.

Afterwards the repository item representing the value on the website and the attribute of the “Get Value”-action should access are chosen. The attribute holding the given temperature value is “InnerText”.

This step needs to be done for both Celsius and Fahrenheit values. In the upper right corner of the website the unit of the temperature can be changed.

At the end of the first step the “GetValue” module should look like this:

Note: The temperature value should not be used as identification criteria! The test will only work if the temperature is the same as when it had initially been identified. This can easily be changed by using the Path Editor in Ranorex Spy: Uncheck the “innertext” attribute and check a different appropriate attribute, e.g. “class”.

Step 2: Creating a Variable in Module 2

The step of creating a new variable needs to be repeated for every module the value from the first module should be used in. Here it is the module “ConvertValue” where a value is going to be converted from Celsius to Fahrenheit.

Firstly, the value from the previous module is used for the Celsius text field on the mentioned website. After that the result is validated in a user code action.

After recording and creating the needed variable, the module should look similar to this:

Note: For identification purposes, it would be easier if variables belonging together have the same name. However, this is only a recommendation and not a requirement.

Step 3: Connecting Variables in different Modules to one Parameter

In order to connect all needed variables to each other, a parameter needs to be created.

This is done by right-clicking the test case in the test suite view and clicking “Data Binding” in the context menu.

The test case properties pane will be opened:

Here it is necessary to add two rows in the “Parameters”- section of the window – one for each shared variable.

By clicking the drop down menu “Module Variable”, the variables associated with this parameter (“varTemperature(GetValue)” and “varTemperature(Convert Value)”) can be checked.

Finally, the test suite should look like this:

Testing the Solution

Now it is time to test the solution. This can be done by pressing “Run” in the test suite.

Note: If “Play” is clicked in one of the modules, the variables won’t be bound. In this case the default values of the variables are used.

The report file should look like this:


In this blog post you learned how to share variables from one module to another. There is one main concept which is always the same for every new module added to the test suite: Firstly a new variable in this specific module is created and then it is connected to a parameter of a test case.

Note: If a variable needs to be shared across test cases, it is almost the same procedure. The only difference is that a global parameter or a parameter in a parent test case is taken. A global parameter can be created in the test suite properties pane.

If something was unclear in this blog post, feel free to ask in the comment section or have a look at the following chapters in our user guide:


Categories: Vendor

EnterpriseDB Announces MongoDB & Hadoop Extensions

Software Development Tools Directory - Mon, 07/28/2014 - 17:59
EnterpriseDB has announced the first release of two new extensions that expand PostgreSQL's ability to seamlessly integrate information from big data and NoSQL-only solutions. Providing a single view of data across multiple sources breaks dow ...
Categories: Vendor

MuleSoft Brings Connectivity to Microsoft .NET Applications

Software Development Tools Directory - Mon, 07/28/2014 - 17:57
MuleSoft has announced new solutions for connecting Microsoft technologies within the cloud-enabled enterprise. The new solutions provide out-of-the-box connectivity to a vast library of Microsoft products, including Microsoft SharePoint, SQL Ser ...
Categories: Vendor

XebiaLabs Releases Updates to XL Deploy and XL Release

Software Development Tools Directory - Mon, 07/28/2014 - 17:54
XebiaLabs announced new features and enhancements to its XL Deploy and XL Release products. Included are updates to its dashboards and reporting functions designed to improve feedback on the entire software build and release process. XebiaLabs pr ...
Categories: Vendor

StrongLoop Announces Node.js API Server for Developing, Securing and Scaling REST APIs

Software Development Tools Directory - Mon, 07/28/2014 - 17:52
StrongLoop has announced the immediate availability of the StrongLoop API Server which makes it easy for developers to rapidly develop, deploy, secure and scale REST APIs written in Node. The ubiquity of mobile devices along with the rapid expans ...
Categories: Vendor

Online Short Course: Requirements Management with Polarion LiveDocs

Polarion Software - Mon, 07/28/2014 - 17:33
Did you know there's an online short course in Requirements Management using Polarion LiveDocs? It's actually been around for a while. Whether you're evaluating Polarion, or have had it for some time, it can be a really useful resource for getting up to speed.
Categories: Vendor

Tasktop Sync 3.6 Extends Requirement and Test Synchronization to Systems and Product Delivery

Software Development Tools Directory - Mon, 07/28/2014 - 17:00
Tasktop has announced Tasktop Sync 3.6 with continued innovations for support of exceptionally complex integration scenarios. Building on the advanced Artifact Relationship Management capabilities in the previous release, Sync 3.6 supports the in ...
Categories: Vendor

Neotys Announces NeoLoad 5.0 Enterprise Load & Performance Testing

Software Development Tools Directory - Mon, 07/28/2014 - 16:47
Neotys has announced NeoLoad 5.0, an enhanced version of its load and performance testing solution. The release of NeoLoad 5.0, now available with a Free Edition download, adds powerful new capabilities for mobile applications and web application ...
Categories: Vendor

Hansoft Brings Agile Metrics Closer to Development

Software Development Tools Directory - Mon, 07/28/2014 - 16:26
Hansoft brings Actionable Agile Metrics to developers, managers and executives with the release of Hansoft 8. Hansoft 8 uniquely brings Actionable Agile Metrics to the entire organization by combining Program Management with Business Intelligence ...
Categories: Vendor


Software Development Tools Directory - Mon, 07/28/2014 - 15:21
DotCi brings ease of build configuration of cloud ci systems like travisci and ease of runtime environment configuration of docker to jenkins.
Categories: Vendor


Software Development Tools Directory - Mon, 07/28/2014 - 15:20
Mithril is an open source Javascript client-side MVC framework, a tool to organize code in a way that is easy to think about and to maintain.
Categories: Vendor