View previous topic :: View next topic
|
Author |
Message |
dandapani
New User
Joined: 13 Dec 2005 Posts: 7 Location: banglore
|
|
|
|
Hi ,
Can any one pls share your ideas about Mainframe testing .Actually what type of roles & responsibilities , type of testing ,onlline or batch ,any automated tools,how will test batch programs by using any tool.etc
I know its totally different from company to company.
hope we can share our ideas and make use of it .
Thanks in advance.
Dhans. :roll: |
|
Back to top |
|
|
toddnugen
New User
Joined: 01 Nov 2006 Posts: 9
|
|
|
|
Quality and Endeavor play successful role in testing while speed aims at productivity generally. Testers need to understand thoroughly the principals that have neen applied since early 70s or before that.
Test Sample: Define, Case test, Linear/Regression test
Top down test and Bottom Up test
Unit test, System test and Parallel test
Location test: Unit and Network
Time test: Schedule and Zones
Hardware test for related devices
Software test for operating system Platforms, database; etc.
No magic for how good the software or tools used, missing any category on these check lists will sure fail next phases. |
|
Back to top |
|
|
jagdishmudiraj
New User
Joined: 25 Apr 2007 Posts: 7 Location: gurgaon
|
|
|
|
Hi
Roles and responsibilities as your point of concerns starts
from technincal spec given you need to prepare
1. Detailed System Spec
2. Detailes Test Plan(Which includes all the Test Scenarios)
3. Data Preparation( which again plays a Crucial role)
4. Finally Execution. |
|
Back to top |
|
|
mandator10
New User
Joined: 20 May 2007 Posts: 7 Location: Mumbai
|
|
|
|
Can any one answer to this question:
What is Regression Testing?
Savvy |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Hello,
One way to describe regression testing is that after changing a bit of code, you not only test the change that was intended, but you also test everything else the program does. Sometimes an innocent looking change in one part of the code causes another part of the code to cease working. If this "broken" piece of code is seldom used, it may be many executions before the problem is detected (especially if other innocent changes have been made to the program after the problem change).
Places that do a good job of testing have a contrived test bed that is already proven to flex all of the code properly. Any time a new function is added or an existing function is changed/deleted, new content is added to the contrived test data and the program re-run.
In this type of environment all of the expected values (succssful and planned-for errors) are documented and the test run is validated against expected output.
Sometimes, this testing includes timing tests to ensure modifications do not cause performance problems. |
|
Back to top |
|
|
mandator10
New User
Joined: 20 May 2007 Posts: 7 Location: Mumbai
|
|
|
|
Thank u very much for the useful reply dick.
Savvy |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
You're welcome |
|
Back to top |
|
|
|