Software Testing

Software Quality Assurance Policy

2009-07-02T16:29:00.002+05:30

This document is a draft version of JISC policy and guidelines for software quality assurance in JISC funded projects. It is intended that the policy and guidelines outlined in this document be piloted with the Distributed eLearning Programme’s eTools projects allowing the refinement of the policy/guidance.

for more details visit link
http://www.macrotesting.com

Software Engineering Metrics

2009-07-02T16:15:00.003+05:30

We hear too often that few companies establish measurement programs, that fewer succeed with them, or that many of the companies who have established metrics programs have them in order to conform to criteria established in the Capability Maturity

for more best practices plz visit
http://www.macrotesting.com

Client/Server Software Testing

2009-07-02T15:59:00.002+05:30

Client/Server system development is the preferred method of constructing cost-effective department- and enterprise-level strategic corporate information systems. It allows the rapid deployment of information systems in end-user environments.

for more information visit
http://www.macrotesting.com

Software Testing – A Novel Approach

2009-07-02T15:27:00.002+05:30

Testing is in integral activity for any type of product development, be it software product development or any other. This paper attempts to identify various issues related to testing that a typical software development company faces.

you can visit this link to download the entire document
http://www.macrotesting.com

Testing a Complete J2EE

2009-07-02T13:55:00.002+05:30

Sheldon Wosnick published an article on completing and testing a complete J2EE application using WebSphere Studio. That article was based on the very first beta of WebSphere Studio

You can download complete document at http://www.macrotesting.com

Software Testing Techniques 2E

2009-07-01T15:34:00.004+05:30

Every professional and commercial software development organization spends a great deal of time in the testing and validation of their software. The testing process, driven either by legal or financial requirements, can be expensive and may thwart the planned deployment of the application.
Many studies indicate that the testing process can even take three times as long as the actual coding itself.

for more information visit
htp://www.macrotesting.com

Java Open Source Programming

2009-07-01T15:26:00.003+05:30

Book Name: Java Open Source Programming: with XDoclet, JUnit, WebWork, Hibernate

for more information visit
http://www.macrotesting.com

Find the Bug A Book of Incorrect Programs

2009-07-01T15:15:00.003+05:30

You'll learn better ways to read code, understand it -- and above all, improve it. Whether you're building new systems or maintaining someone else's, you'll find bugs earlier, faster, with less frustration... and write cleaner code to begin with.

for more details visit
http://www.macrotesting.com

Apache The Definitive Guide

2009-07-01T15:09:00.003+05:30

Updated to cover the changes in Apache's latest release, 2.0, as well as Apache 1.3, this useful guide discusses how to obtain, set up, secure, modify, and troubleshoot the Apache software on both Unix and Windows systems. In addition to covering the installation and configuration of mod_perl and Tomcat, the book examines PHP, Cocoon, and other new technologies that are associated with the Apache web server.

for more information visit link
http://www.macrotesting.com

Autobench-2.1.1

2009-06-30T15:29:00.002+05:30

Autobench is a collection of scripts designed to automate the process of benchmarking a Webserver (or for conducting a comparative test of two different Webservers).

for more details visit
http://www.macrotesting.com

LogCrawler

2009-06-30T15:00:00.003+05:30

LogCrawler is an ANT task for automatic testing of web applications. Using a HTTP crawler it visits all pages of a website and checks the server logfiles for errors. Use it as a "smoketest" with your CI system like CruiseControl.

for more details visit link below
http://www.macrotesting.com

DECOMPILER 3.9

2009-06-30T14:45:00.002+05:30

VB Decompiler is decompiler for programs (EXE, DLL or OCX) written in Visual Basic 5.0/6.0. As you know, programs in Visual Basic can be compiled into interpreted p-code or into native code. Since p-code consists of high-level commands, there is a real possibility to decompile it into the source code (of course, the names of variables, functions, etc. will not be decompiled).

for more information about testing visit
http://www.macrotesting.com

Typemock 4.3

2009-06-30T14:27:00.001+05:30

The Typemock Isolator developer tool is an add in for Visual Studio .NET (vs 2005/vs 2008) that simplifies unit testing by making a cleaner code and eliminating the need to refactor and restructure your code specifically for unit testing.This add in gives the developer tools to isolate, stub or mock any class in the system, such as sealed, abstract, and static classes or methods.

for more detail information visit
http://www/macrotesting

EclEmma - Java Code Coverage for Eclipse

2009-06-30T13:46:00.003+05:30

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. Internally it is based on the great EMMA Java code coverage tool, trying to adopt EMMA's philosophy for the Eclipse workbench.

for more information visit link
http://www.macrotesting.com

WAN Emulator 2.1

2009-06-30T13:37:00.002+05:30

This product, in conjunction with the best load testing tools, such as LoadRunner® (Hewlett-Packard, former Mercury Interactive) or Application Stress Test Tool ® (Microsoft) will give you end-user eye view of the application performance and will help you to identify majority of trouble places, well ahead of the time application sees the world.

for more information visit
http://www.macrotesting.com

phpBugTracker 1.0.4

2009-06-29T16:37:00.002+05:30

phpBugTracker is a web-based bug tracker with functionality similar to other issue tracking systems, such as Bugzilla. Design focuses on separating the presentation, application, and database layers. phpBugTracker is lightweight and easy to install, operate and administer. Most text can be customized for your application.

for more detail information visit this link
http://www.macrotesting.com

PythonQt

2009-06-29T15:41:00.004+05:30

PythonQt is a dynamic and lightweight script binding of the Qt framework to the Python language. It can be easily embedded into Qt applications and makes any QObject derived object scriptable via Python without the need of wrapper code generation.

for more information visit
http://www.macrotesting.com

Wing IDE Professional 3.1.7-1 (MAC OS)

2009-06-29T14:43:00.000+05:30

This high-quality professional integrated development environment (IDE) for Python speeds development time and improves code quality with plenty of powerful code intelligence, editing, testing, and debugging features. Use Wing IDE and Python for rapid development of cross-platform desktop and web applications, enterprise application integration, software testing, and application scripting. Unlike many competing technologies, Wing IDE and Python let you concentrate on building your application-specific functionality.

for more information visit
http://www.macrotesting.com

BullseyeCoverage (Linux)

2009-06-29T13:57:00.000+05:30

BullseyeCoverage is a code coverage analyzer for C++ and C that tells you how much of your source code was tested. Code coverage analysis is useful during unit testing, integration testing, and final release. BullseyeCoverage enables you to create more reliable code and save time. Merge results from distributed testing

for more detail information for software tool visit
http://www.macrotesting.com

LizaJet Installer for Delphi Developers 1.2

2009-06-29T13:50:00.000+05:30

Installation and upgrading are just different modes for this efficient installer. User Dialogs are shown before downloading; only the files of the features your user selects are downloaded, and during upgrading only small patches containing new and changed files are downloaded and installed. Your installation works on all versions of Windows, it handles the network and proxy settings of Internet Explorer, Netscape Navigator and Opera. You can create installations without doing any programming at all, but you can always fall back on Object Pascal Script and on the Script Editor, Dialog Editor and integrated Debugger. Just like in Delphi you can drop visual components, and define properties and event handlers.

for more information visit link below
http://www/macrotesting.com

lemonite

2009-06-29T13:44:00.000+05:30

Unit testing tool that automates J2EE test development and management. Based on JUnit and Eclipse SWT, creating reusable and ready to run tests for J2EE business objects (Servlets, EJBs, POJOs, etc...) and for Web Services becomes very easy.

for more information visit
http://www.macrotesting.com

NetSpotter

2009-06-29T13:15:00.000+05:30

This software is a J2EE and web based network monitoring and testing tool focusing on multicast issues.

for more information visit http://www.macrotesting.com

Load Test Tools Evaluation

2009-06-26T16:41:00.000+05:30

Load Test Tools Evaluation White papers.........

for more details visit tis link below
http://www.macrotesting.com

Automated Test Tools Comparison

2009-06-26T16:24:00.000+05:30

White papers for Automated Test Tools Comparison..........

for more details visit tis link below
http://www.macrotesting.com

AppNavigator

2009-06-26T16:16:00.000+05:30

AppNavigator is the easiest way to create powerful cross-platform automation routines. With AppNavigator you don't have to write a line of code. Just show AppNavigator what to do. AppNavigator sees the screen just like you. Create steps by capturing screen objects graphically. Highlight an object on the screen and then tell AppNavigator what to do with it by selecting from preselected actions. You can even tell AppNavigator what to do if it doesn't find it and benefit from powerful built in failover technology.

for more details visit tis link below
http://www.macrotesting.com

Datatect The Test data Generator

2009-06-26T16:10:00.000+05:30

Datatect® is an intuitive, powerful program for generating a virtually limitless variety of realistic test data to ASCII flat files or directly to RDBMS including Oracle, Sybase, SQL Server, and Informix

for more information visit tis link below
http:www.macrotesting.com

Static Testing

2009-06-26T15:23:00.000+05:30

Static testing is a form of software testing where the software isn't actually used. This is in contrast to Dynamic testing. It is generally not detailed testing, but checks mainly for the sanity of the code, algorithm, or document. It is primarily syntax checking of the code or and manually reading of the code or document to find errors. This type of testing can be used by the developer who wrote the code, in isolation. Code reviews, inspections and walkthroughs are also used.

For More details n information plz go to tis link below

http://www.macrotesting.com

Categorizing Defects by Eliminating 'Severity' and 'Priority'

2009-06-26T15:10:00.000+05:30

eBook: Categorizing Defects by Eliminating 'Severity' and 'Priority'
Description: This article helps you to understand the advancement in defect tracking

Beta Test

2009-06-26T13:53:00.000+05:30

eBook: Beta Test
Description: Tips for running beta test

Bug Report

2009-06-26T13:41:00.000+05:30

eBook: Bug Report
Description: A dozen helpful tips to write a bug report

Methodologies and Techniques

2009-06-25T19:35:00.000+05:30

eBook: Methodologies
and Techniques
Description: This article helps you to understand what is positive and negative testing

Census Bug Tracking and Defect Tracking 6.0 Publisher's description

2009-06-25T18:55:00.000+05:30

eBook: Census Bug Tracking and Defect Tracking
6.0 Publisher's description
Description: Census is a highly scalable Web-based tool for bug tracking and defect tracking that makes it easy to manage project-related issues such as bugs, defects, feature requests, development tasks, support calls, and much more.

Software QA and Testing

2009-06-25T18:38:00.000+05:30

eBook: Software QA and Testing
Description: Free online testing faqs.

Acceptance Test Plan

2009-06-25T16:27:00.000+05:30

eBook: Acceptance Test Plan
Description: An The Acceptance Test Plan verifies that the final deliverable meets the client's requirements.

Testing Java App with Silktest v2006

2009-06-25T15:16:00.000+05:30

eBook: Testing Java App with Silktest v2006
Description: Free eBook on java testing

DzSoft Perl Editor

2009-06-24T19:57:00.000+05:30

DzSoft Perl Editor is a tool for writing, editing, and debugging Perl/CGI scripts. It has a comfortable and intuitive interface both for beginners and advanced programmers. DzSoft Perl Editor is deceptively simple, but it is really a very powerful tool. Has Code Explorer, very comfortable editor with syntax highlighting, syntax check, easy to use breakpoints with variables watch and many other things for easy and comfortable Perl development.

for detailed information visit http://www.macrotesting.com

1st JavaScript Editor

2009-06-24T19:48:00.001+05:30

It is Ajax - JavaScript Editor, Validator and Debugger for beginners and professionals. AJAX developers can use javascript editor as advanced Ajax Editor. Beside rich possibilities of editing scripts (JavaScript, HTML, CSS, VBScript, PHP and ASP) and IntelliSense, Ajax Editor offers built-in JavaScript Debugger which allows you run and debug JavaScript and Ajax code one line at a time

for more details visit htttp://www.macrotesting.com

JavaScript Code Library

2009-06-24T17:13:00.000+05:30

JavaScript Code Library is a powerful multi-language source code Library with the following benefits:1. Built-in library with 50,000++ lines of code2. Quick and powerful search engine3. Powerful printing capability4. Password protection & strong 448 bits encryption (optional)5. User notes & attachments handling6. Favorites & rating support7. Full integration with *all* major programming IDEsAnd much more!!!

Lemo Cobol Development Tool

2009-06-24T16:55:00.000+05:30

Powerful modern development tool for COBOL programmers created by COBOL programmers. Syntax analyzer, source browser, content assistant, refactoring, compilation helps you increasing your performance and quality.

Operating Systems All Windows PC OS
License Type Shareware

Testing is Overrated

2009-06-24T15:38:00.000+05:30

I stumbled across a presentation by Luke Francl called: Testing is Overrated. He could have called it: "programmer testing is overrated" but that doesn't have as much zing to it.

His slides display a refreshing reminder to look for balance in your testing techniques and coverage models. What is especially refreshing is that this is coming from a programmer who is studying testing effectiveness seriously.

Look through the slides and his handout. They provide a nice minimal, complementary and diverse set of testing ideas that when used together can be incredibly powerful.

(If you don't feel like clicking the links, he recommends a combination of the following: programmer unit testing, skilled manual testing, usability testing, and code reviews.)

Update: Apparently I am behind the times, and Matt Heusser blogged about this very topic in August. It's worth being reminded of though. :-)

10 ways to make automation difficult or ineffective

2009-06-24T15:33:00.000+05:30

Here goes another 10 items list for automation. If you are in IT or IT services space and manage/deliver automation solutions -- make sure you stay away from these as these items have high likely hood of making automation inefficient/ineffective and difficult.

This list is an extension of a topic and this list (of 10 items again) for test automation outsourcing

10. Wild Desire to automate 100%

9.Attempting to automate existing test cases without scrutinizing them for “suitability” to automate

8. Mapping test case to script 1:1 linear model – falling prey to deceptive traceability and gold plated reporting.

7.Not building automation solution bottom-up , unidentifiable building block of the solution.

6. Trying only one type of automation or attacking only one layer of the application – Farther you go from code, messier it gets.

5. Focusing only test execution related tasks

4. Treating automation as scripting – ignoring “generally accepted good software development practices for hygiene.

3. Failure to involve developers from the beginning – Not attempting to testability or automatability of the application.

2. Jumping to automation to speed up testing or save cost before fixing testing problems – inadequate, inefficient and broken.

1. Failure to arrive (formulate) at the right mix of human testing and automated test execution.

0. Using Automation as solution to testing problems.

I reiterate that these are applicable mostly to COTS driven, GUI functional Testing automation that is typical in IT/IT services environments. WI might have to rewrite some of these for xUnit type formalized unit testing (that is also automation and some call it even as "testing").

link for Automation tools

http://www.macrotesting.com

Testing Dot Net Applications

2009-06-24T15:11:00.000+05:30

A free eBook on .Net testing

Degrees of Test Automation

2009-06-24T15:02:00.000+05:30

Welcome to the first entry in my discussion of test automation. I'll be starting by discussing the different levels of automation that can be applied to testing. Future posts will cover test case automation vs. execution automation, why automate tests, and how to automate tests.

Test automation covers many different aspects. There are many different elements, each of which can be automated. While the exact elements will vary depending on what is being tested, they general consist of machine configuration, component install, test execution, logging, and reporting. Each of these can be fully automated.

While automated all of the above would reduce the amount of time spent by a human running tests greatly, there are some downsides. Automating all of the aspects has higher upfront development cost than performing some of the steps manually. On projects that are planned to last for a short amount of time, this level of effort might not be justified. The maintenance costs for such a highly automated system can also be higher over time, as there are more aspects of the system which would require updating.

Fortunately the various test stages can be automated independently to different degrees. Movement between stages of a test can also have different levels of automation. For example, machine setup could be done through imaging software initiated by a script. Another script would then be ran (by a tester) to install the software being tested, run the tests, then upload logs to a central location. After this has been completed the logs would be inspected by someone visually to determine if there was a failure that needed investigation.

While this example test process is not fully automated end to end, there is little human intervention, and much of it is limited to executing scripts. One of the downsides is that tester interaction is needed to move from stage to stage. This requires awareness that a previous stage is complete. If each stage does not proactively notify someone that it is complete (via email for instance), a tester is required to at least occasionally observe the automated process. Another problem is that large series of tests can't be started and expected to run to completion overnight or over a weekend (unless someone is present of course).

for more details visit http://www.macrotesting.com

Developing a Test Specification

2009-06-24T14:06:00.000+05:30

Definitions

I’ve seen the terms “Test Plan” and “Test Specification” mean slightly different things over the years. In a formal sense (at this given point in time for me), we can define the terms as follows:

1. Test Specification – a detailed summary of what scenarios will be tested, how they will be tested, how often they will be tested, and so on and so forth, for a given feature. Examples of a given feature include, “Intellisense, Code Snippets, Tool Window Docking, IDE Navigator.” Trying to include all Editor Features or all Window Management Features into one Test Specification would make it too large to effectively read.
2. Test Plan – a collection of all test specifications for a given area. The Test Plan contains a high-level overview of what is tested (and what is tested by others) for the given feature area. For example, I might want to see how Tool Window Docking is being tested. I can glance at the Window Management Test Plan for an overview of how Tool Window Docking is tested, and if I want more info, I can view that particular test specification.

If you ask a tester on another team what’s the difference between the two, you might receive different answers. In addition, I use the terms interchangeably all the time at work, so if you see me using the term “Test Plan”, think “Test Specification.”

Parts of a Test Specification

A Test Specification should consist of the following parts:

* History / Revision - Who created the test spec? Who were the developers and Program Managers (Usability Engineers, Documentation Writers, etc) at the time when the test spec was created? When was it created? When was the last time it was updated? What were the major changes at the time of the last update?
* Feature Description – a brief description of what area is being tested.
* What is tested? – a quick overview of what scenarios are tested, so people looking through this specification know that they are at the correct place.
* What is not tested? - are there any areas being covered by different people or different test specs? If so, include a pointer to these test specs.
* Nightly Test Cases – a list of the test cases and high-level description of what is tested each night (or whenever a new build becomes available). This bullet merits its own blog entry. I’ll link to it here once it is written.
* Breakout of Major Test Areas - This section is the most interesting part of the test spec where testers arrange test cases according to what they are testing. Note: in no way do I claim this to be a complete list of all possible Major Test Areas. These areas are examples to get you going.
* Specific Functionality Tests – Tests to verify the feature is working according to the design specification. This area also includes verifying error conditions.
* Security tests – any tests that are related to security. An excellent source for populating this area comes from the Writing Secure Code book.
* Accessibility Tests – This section shouldn’t be a surprised to any of my blog readers. See The Fundamentals of Accessibility for more info.
* Stress Tests – This section talks about what tests you would apply to stress the feature.
* Performance Tests - this section includes verifying any perf requirements for your feature.

* Edge cases – This is something I do specifically for my feature areas. I like walking through books like How to break software, looking for ideas to better test my features. I jot those ideas down under this section

* Localization / Globalization - tests to ensure you’re meeting your product’s International requirements.

Setting Test Case Priority

A Test Specification may have a couple of hundred test cases, depending on how the test cases were defined, how large the feature area is, and so forth. It is important to be able to query for the most important test cases (nightly), the next most important test cases (weekly), the next most important test cases (full test pass), and so forth. A sample prioritization for test cases may look like:

1. Highest priority (Nightly) – Must run whenever a new build is available
2. Second highest priority (Weekly) – Other major functionality tests run once every three or four builds
3. Lower priority – Run once every major coding milestone

for more information visit

http://www.macrotesting.com