Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Facts taken care in testing cobol projects

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Testing & Performance analysis
View previous topic :: :: View next topic  
Author Message
awyn

New User


Joined: 11 Feb 2008
Posts: 49
Location: chennai

PostPosted: Wed Sep 03, 2008 10:36 am    Post subject: Facts taken care in testing cobol projects
Reply with quote

Hi,
can anybody tell me what are the facts taken care in testing cobol projects, i mean which files and other things to test in cobol projects.
Back to top
View user's profile Send private message

dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Wed Sep 03, 2008 12:08 pm    Post subject:
Reply with quote

Hello,

In one word - everything.

Every line of code, every field on a map, every entry on a report, every field in every file and database table, every bit of data to be downloaded, every message that will ever be presented by the system needs to be tested. Every interface to other systems must be tested. Every backup/restore/recovery procedure must be verified.

There is nothng built as part of a project that should not be thoroughly, successfully tested.
Back to top
View user's profile Send private message
awyn

New User


Joined: 11 Feb 2008
Posts: 49
Location: chennai

PostPosted: Wed Sep 03, 2008 7:17 pm    Post subject:
Reply with quote

Can you please tell me which is the most tedious jobs in testing cobol projects.
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Wed Sep 03, 2008 9:12 pm    Post subject:
Reply with quote

Hello,

Quote:
which is the most tedious jobs in testing cobol projects.
Making sure you have identified every possible test criteria.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8057
Location: East Dubuque, Illinois, USA

PostPosted: Wed Sep 03, 2008 11:33 pm    Post subject:
Reply with quote

I like black box testing, where you take somebody who knows nothing about the system, set them in front of the screen, and see how long it takes them to blow up the system using the documentation. For an online system, under a minute isn't that rare.

With white box testing the problem is ensuring you're testing all possible data paths. I did automatic test case generation for a batch system one time and wound up generating over 22,000 test records -- but did they ever test that system completely!

In the best possible world, the tester and developer are both given the specs and independently do their thing, one creating test cases and the other creating the system. The test cases may not match what the system does, but the discussions about why the differences are always illuminating.
Back to top
View user's profile Send private message
PeD

Active User


Joined: 26 Nov 2005
Posts: 456
Location: Belgium

PostPosted: Thu Sep 04, 2008 12:33 am    Post subject:
Reply with quote

Just surprised you mentioned "cobol" projects !
Testing is one of the most critical part of a project. Often too much close to the end, in a hurry.

But why "cobol"? Also valid for PL/I, Telon, CSP, ASM, C, EZT, RPG, .....
Do you believe the approach is different for Cobol?
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Thu Sep 04, 2008 12:03 pm    Post subject:
Reply with quote

Probably it's a never ending discussion. Testing would differ from phase to phase - I had a "Regression Testing' in one project & the testing reached to 12000+ test conditions, there were three systems involved in that project & 12000+ were only for my system..! As robets has said - but did they ever test that system completely..!

I belieave there should already be a "policy" in use at your shop for this, but if this is first time you/your shop thought aboput this - I would suggest start with general scenarios of your production so that you are sure at least "BAU" (Business As usual) is not distrubed, once that is done move on to more rare (& more complex) production scenarios..& yes as PeD said in case you have experience with other technologies- aprroach doesn't differ with COBOL.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> Testing & Performance analysis All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Testing rerad cursor for status with ... John F Dutcher DB2 8 Fri May 19, 2017 9:35 pm
This topic is locked: you cannot edit posts or make replies. Cobol GUI (like Editor) Kala Mainframe COBOL Programming 14 Wed May 10, 2017 12:30 pm
No new posts IMS T-Pipe queue counts in a COBOL Pr... Siva NKK Kothamasu IMS DB/DC 0 Tue May 09, 2017 6:31 pm
No new posts COBOL Code Parsers and Lineage Establ... balimanja COBOL Programming 2 Tue May 02, 2017 3:30 am
No new posts Cobol upgrade - source code missing f... gthmrj IBM Tools 1 Wed Apr 26, 2017 6:04 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us