Making a shift from developers profile to Mainframe Testing

vikas.gupta · New User Joined: 16 Aug 2006 Posts: 1

Hi all
I am a mainframe developer with two years of Experience in Developers Profile. I want to know that should i a make a transition to Mainframe testing.
And what all are the merits and demerits of making this move?
The profile of mainframe testing is preparing the system test cases, and then testing the same.
Do we get more domain knowledge in Testing projects as compared to development projects ?

PeD · Posted: Thu May 29, 2008 6:59 pm Post subject:

You must have order, method and discipline.
A special mind : always be suspicious, never thinking that a little thing is not a consequence of a change in program.
Every non expected result must be reported and reported with documentation ( using Quality Center or other tools ).

They are various kind of tests : integration tests, performance tests, volume tests, regression tests, stress tests. �..

You can test a mall cluster of programs or a whole day or night of production. You need to know the expected results, discuss with business analysts, with system team, with Capacity team, �.
And you will have to know a lot of tools or technic : Strobe, File Aid, Ecomp, CA7, report Excel, Word, DB2, CICS, zOS, Sort, backup, recovery, etc etc

Maybe you will want to build some proper tools in REXX, VBA, panel, routines to help you in your work.

It is a wonderful world.

There is not a lot of �bravo� if it is working, there is a lot of danger if it is not working in production. �

But one thing you have to know : tests are crucial, essential, but you are at the end of the chain : so if previous team have delay, you will also start later, but I know by experience that the final date, the launch date will not be delayed and then the focus is on you.

I repeat : �code� is nothing. Correctly testing a system is great !!!!

Anuj D. · Posted: Thu May 29, 2008 7:07 pm Post subject:

Well,

It's a question of personal choice. Lately I was also asked for this so would like to comment here... well, again it's a personal perception of things...my answer was no.

PeD · Posted: Thu May 29, 2008 7:34 pm Post subject:

But the added value is when the tester with a developer background is able - not to just pass the problem to others - but make a pertinent analysis, take good actions and not staying blocked in the tests cycle.

The risk is high, the responsibility is high.

jaspal · New User Joined: 22 May 2007 Posts: 49 Location: mumbai

Hi Vikas,

well i think you have valuable suggestions from different expert who drived through their carriers starting from mainframes.

to develop is something which make you feel you did something new no one ever did like that.....
1). Requirement gathering
2). Talking to business and technology directly
3). Designing a database, designing a test
4). Build a system.

Now come toward testing that development team does:
1) Unit testing
2). system testing
3). Integration testing
4). regression testing
5), UAT testing
6) pre-implementation
7). roll-out
8). post implementation..

Now what you feel what is the best development or just testing.

"you can learn testing along with development , but can't learn development along with testing only "
)

ksk · Posted: Mon Jul 28, 2008 9:56 am Post subject:

Vikas,

What is the reason behind to make a shift into Testing from Development as you have already 2 years of expereince in development. I have seen some people (and they asked me for the same) who thinks Testing is easy and Development is hard (this is comparision to Mainframes Testing) and wants to make shift to testing to have a cool life.

Is this the reason or anything else behind your thinking?

Regards,
KSK