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

Mahesh Srivatsavi · New User Joined: 09 Sep 2008 Posts: 2 Location: Banglore

I am also in the similar transition,Worked as a mainframe developer for two years,due to Project Constraints I was made to take up Mainframe testing.
At starting when I joined Mainframe testing as every one I have similar Perception that testing is easy and very cool job and any one can do that but later on I came to know that it is not.

Through my experience I found the following merits in Mainframe testing.

1)Need to have a through knowledge of end to end flow of the application.
(So this helps to know the overall application and how it runs).
2)we have to gothrough whole use cases,Processes and discuss with the Business analysts,Developers,Peers how the application is going to satisfy user requirements and accordingly we need to prepare test design and test cases.
3)Though the testers job is to find the defects and raise to the developer team , sometimes they need to solve abends by themselves and then go for developers help.
4)There will be some projects in which the front end will be java and the backend will be mainframe at time it is testers responsibility to whome to assign the defect and in some instances it may be due to environment issues the errors may crop up.(Tester has to take up responsibility).
5)The project may delay due to some reasons but the end date will be fixed here comes the role of tester , he has to test every thing in the given time and the same time assure the quality of the software.
6)A company can assure the quality product to the client only when it undergone the complete process of testing.

Atlast I conclude both mainframe developing and testing has equal importance both has their own Pros and cons.

It is a advise to the people donot come from development to testing thinking Mainframe testing is cool than compared to development(It is merely misconception).

Aaru

Hi,

PeD · Posted: Mon Dec 29, 2008 6:08 pm Post subject:

expat · Posted: Mon Dec 29, 2008 6:11 pm Post subject:

And I won't ask about the night job

muthuvel · Posted: Mon Dec 29, 2008 6:18 pm Post subject:

It finally seems to be a debate of Development Vs Testing

Every Job has its own merits and demerits
"DO WHAT YOUR ARE COMFORTABLE IN DOING"

dick scherrer · Posted: Mon Dec 29, 2008 9:45 pm Post subject:

Hello,

PeD · Posted: Mon Dec 29, 2008 10:01 pm Post subject:

I want to add that it is not always the developer's fault.
Sometimes they do not have the right tools or environment ( testing environment set up is not an easy task - often part of production elements are missing ).

Also I firmly believe that there is a lack of education in testing.
Not only in IT world.
See around all stuff not working in industry, in instrument, toys, ...
not only economy on the product, but lack of testing, or lack on "how to test".

Don' forget also that testers are sometimes ( like me ) former developer.

Terry Heinze · Posted: Tue Dec 30, 2008 12:09 am Post subject:

"It is often better to meet the deadline with code that fails - delivering non-working code "on time" and fixing/re-writing it later often has less penalty than delivering a fully working application late."
Reminds me of one of my favorite sayings, "If you don't have time to do it right, when will you have time to do it over?!"

PeD · Posted: Tue Dec 30, 2008 12:38 am Post subject:

Production stability? Tell that to the management and the clients !!!