Framework and tools for managing testing and monthly releases?

I'm not anywhere close to being an expert on professional QA and testing but I do work with it as part of managing a IT system at work. To be honest, we are not very mature when it comes to using an actual framework or methodology and our tool support is quite lacking too. This has been painfully obvious in course of us upgrading to the newest version of the IT system.

I'm afraid tool support has more or less been decided. Oracle Primavera has been used so for managing projects - and from my perspective - issues. Quality Center has been used so far functional testing of the new version of the IT system. Service Manager has been chosen as the new ticket system for support of the IT system. I'll be working in that landscape in the future, not really sure what tool will be used.

What I'm looking for is more in terms of a framework or methodology. We have in-house developments and vendor-developed enhancements that needs tracking and QA. We do automated testing, regression testing of our databases before releases and functional/user acceptance testing. Any ideas?

Replay

At my former work we were using the gate process.
In practice that meant you have:

  • fixed inputs for the testing (the software, documentation, tools).

And at the end of testing you provide:

  • fixed output (test report supported by entries in bug the tracking system).

The test process was described by a document called test plan which included: Time estimate, Testing scope, Test types to be performed ... etc. The test report was one of the input for the go meeting where was decided if the monthly update will be released to customers or postponed.
The test report was quite straightforward. Aside of description of testing environment and the testing inputs, contained a list of tests performed (regression, functional, performance, integration) along with the result: passed/failed. When test failed it had to be cooperated by an incident number.

This is just my practical experience from the point of view of everyday testing. It's not a complete methodology, but it might help. Esp if you google something more about the Gate process.

Category: automated testing Time: 2012-07-20 Views: 1

Related post

iOS development

Android development

Python development

JAVA development

Development language

PHP development

Ruby development

search

Front-end development

Database

development tools

Open Platform

Javascript development

.NET development

cloud computing

server

Copyright (C) avrocks.com, All Rights Reserved.

processed in 0.112 (s). 12 q(s)