Software Testing Tools Blog – Testertools

Zanebug is an advanced unit testing application for .NET.

It supports existing NUnit tests, performance metrics, multiple test iterations, in-depth error information, pass / fail stats, perfmon integration, result graphing, etc.

• Zanebug introduces the Repeat attribute for methods, its works in this way:
• In NUnit you have Setup, and TearDown attributes, that do initialization and termination code for the TestFixture. A nice feature of Zanebug is Method specific setups and teardowns:
• The graphical user interface of Zanebug is more friendly and has more information than NUnit.

Visit Testertools.com for Zanebug

Typemock,  the leading provider and pioneer of unit testing solutions announced today the official launch of Isolator ++.

Isolator ++ is the first isolation framework that allows developers to conduct easy unit testing for C++. As opposed to other unit testing solutions that require many sections of code to be modified in order to test it, Isolator ++ allows the user to mock any part of the code without any alterations. It also enables organizations to ensure that their final product meets industry standards.

The launch of Isolator ++ demonstrates Typemock’s ability to now offer solutions for easy unit testing for windows C++ developers in addition to .Net.

Isolator++ enables testing of any C/ C++ code (including complex code such as statics, globals and non virtual method) by allowing the user to intercept and fake their behaviours. The user can write tests with minimal lines of code, a major improvement on other frameworks which require multiple lines to make effective readable tests. The API is specifically designed to make tests more concise, more resistant to production code changes and easier to understand for new users. Isolator ++ works with all testing frameworks including Google Test and UnitTest++.

“Adding C++ solutions to our product range is a natural step for Typemock” commented Eli Lopian Typemock‘s founder and CEO. “With a growing number of developers writing in C++, especially with the increased popularity and demand for smart phones and other advanced technologies, there is an obvious need for an easy solution for C++ unit testing which ensures that the final product surpasses all regulatory requirements. This is imperative for the military, avionics, automotive and medical device industries where an error in the code can be critical.”

JetBrains, a provider of productivity-enhancing development tools, introduced dotCover, a new code-coverage tool for .NET developers, and dotTrace 4 Performance, a reworked version of its .NET profiling tool.

According to sdtimes.com the tool extends Microsoft Visual Studio and its .NET productivity offerings,

dotCover, an extension to Visual Studio, highlights code that was not covered during a unit test and detects which unit tests covered a particular area in the code. This helps .NET developers ensure that every line that should be covered in a unit test is covered, according to the Prague-based company. The tool also aggregates data from multiple coverage sessions, merges collected snapshots and generates XML-based code-coverage reports.

Working within Visual Studio 2005, 2008 or 2010, dotCover analyzes statement-level code coverage in .NET Framework and Silverlight applications, and it integrates with JetBrains’ ReSharper unit testing tool set.

dotCover also provides a console utility, enabling users to use it with a continuous integration server.

“We felt it would be fitting to give .NET developers a tool to help them see how successful they are in their unit-testing practices,” said Oleg Stepanov, .NET division project lead for JetBrains. “[dotCover enables] developers to instantly see any lapses in code coverage, and at the same time integrate into corporate development and reporting workflow,” he added.

In addition to dotCover, dotTrace 4 Performance is an upgrade from JetBrains’ .NET profiler offering. After being an all-in-one memory and performance profiler, dotTrace splits into two products, the company said. dotTrace 4 Performance is the .NET performance tool and will be followed by the introduction of dotTrace 4 Memory in several months.

This reworked tool helps .NET developers get accurate information on performance bottlenecks in a variety of .NET applications, including those built on .NET Framework 4, .NET Compact Framework 3.5 and Silverlight 4.

With dotTrace 4, users can profile complex desktop and server applications as well as remote applications. They can also assess how removing a particular bottleneck would affect the overall application performance, the company said.

dotCover is offered now until Jan. 1, 2011, at an introductory price of US$49 per personal license or $99 per commercial license. All licenses include one year of free upgrades and technical support.

dotTrace 4 Performance comes in Standard and Professional editions. Commercial pricing starts at $399. Users can also purchase a bundle of dotTrace 4 Performance and dotTrace 3.5 Memory, a memory profiler with support for the latest .NET Framework, at a discounted price. Those with licenses purchased on or after Dec. 17, 2008, can be upgraded to dotTrace 4 free of charge.

froglogic GmbH have announced  that Squish 4.0, a major new release of its leading, crossplatform and cross technology GUI test automation tool is now available.

Squish can test applications based on a variety of GUI technologies, including Nokia’s Qt Software Development Frameworks,  Java SWT/Eclipse RCP and AWT/Swing, Mac OS X Carbon/Cocoa, native Windows eg MFC,  Web/HTML/AJAX,  iPhone/iPod/iPad CocoaTouch

Squish can also test applications on many different platforms, such as Windows, Linux and various Unixes (Solaris, HP-UX, AIX, etc.) and Embedded platforms.

Squish stands out from other GUI testing tools by giving test engineers the freedom to record and write tests using familiar scripting languages such as JavaScript, Perl, Python, and Tcl. Furthermore, Squish provides extremely tight integration with the specific GUI technologies it supports. This gives testers unprecedented access to the internals of the applications they are testing (to data items, controls, and widgets, etc.), and also leads to the production of very robust and stable GUI tests.

Squish 4.0 delivers many major new features including, Complete compatibility with existing tests created with Squish 3.x., A completely new cross-platform GUI test development environment (IDE) based on Eclipse technology.  A new Squish edition that supports the automated GUI testing of native Windows applications based on toolkits such as MFC, .NET, Windows Forms, Visual Basic, PowerBuilder and so on as well as aA new Squish edition that supports automated GUI testing of CocoaTouch iPhone, iPod Nano and iPad applications.

“With Squish 4.0 we have broadened Squish’s scope to encompass more GUI technologies, and at the same time made Squish easier and more convenient to use, as well as more flexible and powerful. Throughout the development of Squish 4.0 we made technical previews and betas available to customers and used their feedback to ensure that we stayed focused on and responsive to our customers’ practical needs. We are very excited to finally release this major new version of Squish to the public.” said Reginald Stadlbauer, CEO and co-founder of froglogic.

A 10 minutes introduction video to Squish 4.0 is available at froglogic.com.

Infragistics, the experience design software company and world leader in user interface (UI) development tools, today announced that the 2010 Volume 2 version of NetAdvantage for .NET will include the  ASP.NET toolkit which is fully compatible with the Mono framework from Novell.

With the most powerful UI controls available for ASP.NET, Infragistics enables .NET developers to rapidly build and style high-fidelity, full-featured line of business applications and deploy in a Linux environment.

What’s New in This Release

4 Brand New Controls – WebCaptcha™, WebRating™, WebExcelExporter™ & WebScriptManager power lots of new scenarios to build Killer Apps using NetAdvantage® ASP.NET controls.

Control Enhancements – WebHierarchicalDataGrid™ row filtering, WebDataTree™ Drag & Drop and left & right orientation for WebTab™ headers.

Full ASP.NET 4 & VS 2010 support – JavaScript IntelliSense, code snippets, design surface for SharePoint support, full ASP.NET 4 compatibility including Domain DataSource support integrated with all data-bound controls.

Windows 7 Style Sets – New style sets with the professionally designed look and feel of Windows® 7 operating system for our controls in your browser-based, Web applications.

To download the trial version of Volume 2 version of NetAdvantage for .NET click here

NMock is a dynamic mock object library for .NET. Mock objects make it easier to test single components—often single classes—without relying on real implementations of all of the other components. This means we can test just one class, rather than a whole tree of objects, and can pinpoint bugs much more clearly. Mock objects are often used during Test Driven Development.

NMock 2.0 Release Candidate 2 is now available! The original NMock was a .NET port of the Java-based DynaMock, whereas NMock 2.0 is inspired by the newer jMock library. Expectations are defined using a much more “conversational” style, including plenty of syntactic sugar to improve clarity.

A dynamic mock object: * takes on the interface of another object, allowing it to be substituted for a real one for testing purposes.
* allows expectations to be defined, specifying how the class under test is expected to interact with the mock.
* fails the test if any of the expectations are violated.
* can also act as a stub, allowing the test to specify objects to be returned from mocked methods.

Features specific to NMock: * expectations are specified beforehand and verified on the fly as the code under test is being executed, rather than afterwards using assertions. This has the advantage that mocks fail fast, allowing you to easily pinpoint the exact point the test failed, using a stack trace or debugger.
* mock implementations of interfaces are generated on the fly at runtime, which avoids having to add a code generation step to the build.
* error messages clearly show the reason for the failure.
* flexible expectations can be built up using the constraint library.

The best way to see how NMock works is to read the Quickstart (5 minutes) or the Tutorial (15 minutes). Developers who already have experience with mock objects will find everything they need to know on the Cheat Sheet.

Goto TesterTools for more detail.

Today automated software testing plays a vital role in many software development and web application projects.  At XBOSoft, we specifically developed XBO ONE™ Test Automation methodology to deliver cost-effective automated testing for small companies.

It begins with our common sense approach of where and when to use automation. For example, tests that are run many times, such as build verification tests, regression tests, and tests that include many simple and repetitive steps are classic candidates for web application automated testing and software automated testing.  However, if an application or software is not yet stable, then it may make sense to postpone any automated testing efforts.  Automated testing should not be considered a replacement for manual testing, but rather an enhancement.

XBO ONE™ Test Automation Benefits

• Proven methodology that delivers significant cost savings for small companies.

• XBOSoft can quickly determine which parts of the application to automate and which are best suited to manual testing.

• Test automation expertise and proficiency for Windows, .NET, Java, web pages, web servers, web applications and web services.

• Proven experience working with a variety of tools, such as Rational Robot, Borland’s SilkTest, HP’s WinRunner and QuickTest Pro, Compuware, etc.

• Experience in testing multiple operating systems, databases, and application servers with automated test harnesses to rapidly switch platforms for maximum coverage.

XBO ONE™ Test Automation Methodology

XBO’s software automation methodology was developed with small companies in mind and an objective to significantly boost testing productivity while keeping costs and implementation efforts to a minimum. Key elements of our methodology are:

1. Ascertain software‘s suitability for automation.

2. Review Automation Checklist; such as:

a. Can the test sequence of actions be defined?

b. Is it necessary to repeat the sequence of actions many times?

c. Is it possible to automate the sequence of actions?

d. Are you testing non-UI aspects of the program?

e. Do you need to run the same tests on multiple hardware configurations?

3. Assign & Organize Testing Team .When multiple team members are automating tests, develop common scripting architecture, code, and objects for maximum productivity.

4. Utilize test script modularity framework where appropriate (ie. Create small, independent scripts that represent modules, sections, and functions of the application-under-test).

5. Manage automation process:

• Share and maintain test assets in XBO’s central application repository.

• Propagate script changes to all testers through XBO’s application repository.

• Track which test cases are automated and which are manual, and prioritize which cases get automated first for maximum results.

• Manage script scheduling and execution.

• Optimize the Test > Fix > Verify process to automatically push new defects into the defect tracking workflow.

• Compare versions of scripts for differences, merge changes, and store scripts with other development assets, such as requirements documents, test data, design documents, and source code.

View TesterTools dedicated page for this tool.

Lightweight Test Automation Framework is an integration testing tool, which works by scripting the web browser to perform a sequence of actions against your application’s UI – entering text and clicking links and buttons exactly as a real user would – and then checking that the expected results can be seen in the browser window.

Just in case you don’t know the difference between unit testing and integration testing:

Unit tests work against the API of a particular component in your code.  Ideally, they test only that single isolated unit (hence the name), which allows them to pinpoint any problems exactly where they occur.  Unit testing tools for .NET include NUnit, mbUnit, and xUnit.

Integrations tests combine multiple components.  Typically, they work at the UI level to test that your JavaScript, your HTML, your controller code, your model code, and your database all work together.  Integration testing tools for .NET include Selenium, Watin, and Lightweight Test Automation Framework.

View TesterTools dedicated page for this tool.