Skip to main content

Forbes IT Research Library

TITLE: The pros and cons of automated software testing
PUBLISHER: IBM
TYPE: Video

TITLE:Best Practices for Implementing Automated Functional TestingSolutions
PUBLISHER: Hewlett-Packard Company
TYPE: White Paper

TITLE: Customer Perspective White Paper: Optimizing Manual Testing with Business Process Testing
PUBLISHER: Hewlett-Packard Company
TYPE: White Paper

TITLE: The Business Case for Outsourcing Software Testing to a SeparateVendor
PUBLISHER: LogiGear Corporation
TYPE: White Paper

TITLE: HP TestDirector for Quality Center Software
PUBLISHER: Hewlett-Packard Company
TYPE: Data Sheet

TITLE: Better/Faster/Cheaper..Essentials of Test Data Management
PUBLISHER: IBM
TYPE: Webcast

TITLE: Testing SOA Applications with Rational Quality Management Solutions
PUBLISHER: IBM
TYPE: Webcast

TITLE: Pre-Flight Builds: What They Are, Why You Should Care and How to MakeThem a Reality
PUBLISHER: Electric Cloud
TYPE: Webcast

TITLE: How to Capture Performance Requirements
PUBLISHER: CA
TYPE: Webcast

TITLE: How to Automate Testing without Aggravating Testers
PUBLISHER: Hewlett-Packard Company
TYPE: White Paper

TITLE: Automated Source Code Analysis - When' Why' and How to Leverage Source Code Analysis Tools
PUBLISHER: Klocwork
TYPE: White Paper

TITLE: Software Quality Management
PUBLISHER: IBM Software Group
TYPE: White Paper

TITLE: Shunra - What Every Software Developer Needs to Know about theNetwork
PUBLISHER: Shunra
TYPE: White Paper

TITLE: Security & Robustness Testing Justification; Solution Fit, Cost/Benefitand Success Factors
PUBLISHER: Codenomicon, Ltd.
TYPE: Webcast

TITLE: Best Practices for Software Performance Testing
PUBLISHER: Hewlett-Packard Company
TYPE: Podcast

TITLE: Automate Performance Testing to Predict System Behavior and ImproveApplication Performance
PUBLISHER: Hewlett-Packard Company
TYPE: White Paper

TITLE: Improving Visibility of the Software Development Process
PUBLISHER: Borland Software Corporation
TYPE: Webcast
Labels:

Comments

Post a Comment

Popular posts from this blog

Why to do Software Testing?

Regardless of the limitations, testing is an integral part in software development. It is broadly deployed in every phase in the software development cycle. Typically, more than 50% percent of the development time is spent in testing. Testing is usually performed for the following purposes: To improve quality. As computers and software are used in critical applications, the outcome of a bug can be severe. Bugs can cause huge losses. Bugs in critical systems have caused airplane crashes, allowed space shuttle missions to go awry, halted trading on the stock market, and worse. Bugs can kill. Bugs can cause disasters. The so-called year 2000 (Y2K) bug has given birth to a cottage industry of consultants and programming tools dedicated to making sure the modern world doesn't come to a screeching halt on the first day of the next century. [Bugs] In a computerized embedded world, the quality and reliability of software is a matter of life and death. Quality means the conformance to the ...
1 comment
Read more

HP Quality Center - Best Practices

1.Introduction Quality Center is a test management tool which provides very good features for managing both your manual and automated test cases. This paper highlights the best practices for managing your test cases. When you open Quality center, depending on your rights it display the below mentioned option in the sidebar: 1. Requirements 2. Test Plan 3. Test Lab 4. Defects 5. Dashboard 2.Requirements When you have assigned with the responsibility of developing your test cases in the quality center then you must be wondering where to start with. I am going to share my experience to overcome such a situation. You need to find the solution of some question before you start writing your test cases. 1. Is your requirement developed and available? 2. Is your requirement organized in a logical sequence? If answer to both of the above question is Yes, then you can start with Requirement option in the side bar. In case your requirement is under development, then you keep your...
3 comments
Read more

ABC of Unit Testing

What is Unit Testing? After writing any code, every programmer will do some kind of testing to make sure the code works as expected. This testing is called 'unit testing'. Unit testing is done in different ways. Some programmers write simple test applications to test their own code. Some others simply debug the code and change the values during debugging to make sure the code works fine for different cases. Some facts about unit testing: Unit testing is done by developers. Quality department does different tests, they are not unit tests. Every programmer must do unit testing after finishing development or during development itself. Unit testing can be done by writing separate test applications to call your classes and methods to make sure the classes work as expected. This is called manual unit testing. Unit testing can be automated by writing unit test scripts. This is called Automated Unit Testing. In automated Unit Testing, after writing each class/method, you will write sev...
1 comment
Read more