View previous topic :: View next topic
|
Author |
Message |
ssprabhu
New User
Joined: 25 Apr 2005 Posts: 67 Location: pune
|
|
|
|
Hai
myself sathish now i am working in MAINFRAME TESTING (BILLING DOMAIN). What about the scope for mainframe testing.
every mainframe related companies doing the mainframe testing or not. |
|
Back to top |
|
|
priya
Moderator
Joined: 24 Jul 2003 Posts: 568 Location: Bangalore
|
|
|
|
We have less vacancies for testers comparing to developers in mainframe field. |
|
Back to top |
|
|
Ramakrishna Reddy
New User
Joined: 16 May 2005 Posts: 1 Location: Hyderabad
|
|
|
|
hi,
iam going to be placed in production suppoort/maintenanace.
let me know what is the scope of this part in mainframes. |
|
Back to top |
|
|
harikrishnanrajeev
EXPERT
Joined: 28 Jan 2004 Posts: 37 Location: Trivandrum
|
|
|
|
Mainframe testing, i feel is challenging if u have the interest in dong it. I have worked in system testing for a project. The only difficulty being the enormous documents u have to prepare and the numerous processes u have to follow. Different shops adopt different startegies for system testing.
There aren't many people who are inclined to doing mainframe testing, so if u have real interest in it, then there is less competition for u.
I feel experiance is one thing that matters in mainframe testing, u will be in demand once u gain experiance.
Cheers,
Hari. |
|
Back to top |
|
|
avalanches
New User
Joined: 10 May 2005 Posts: 28
|
|
|
|
Hi,
Mainframe Testing:
I've done Integration/String Testing for 1 & 1/2 years and the system testing for 2 years. From my opinion, if one does these testing, they will become experts in that domain at the business level & high view of the functional level.
Production Support:
I did production support for almost 4 years (24x7). The challenges you are getting would boost your confidence level & technical learning curve steeper. If the system is somewhat UNSTABLE your chance of learning is more to make it more stable. The other side is that this work demands more of your time for the work. Sometimes totally sapping! You have to have a fire for learning from every problem your facing.
Best of Luck,
Cheers,
avalanches. |
|
Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005 Posts: 435 Location: chennai, India
|
|
|
|
I do agree with avalanches about production support.If you have a chance to work in bug filled system then you can learn many things by fixing it.And if your support handles user issues,then I can say that support is one of the best.
One disadvantage in production support is handling pressure.In unstable system,you dont have time to relax yourself,you have to stretch and work more than the office hours,different shift timings and so on...
But once you are experienced then you will overcome.
Its a challenging job.
welcome to the prod support,ramakrishna reddy!! |
|
Back to top |
|
|
Mahesh-Frame
New User
Joined: 06 Sep 2007 Posts: 3 Location: Noida
|
|
|
|
Everthing have its own pros and cons ...thats how it is.
If you want to be business expert in the days to come , opt for prod.support as it opens chances for learning business
otherwise opt for testing.....yes.....testing do have some options for learning business ...but technical sense..I just feel its zero.....no technical exposure will be there in testing....
This world need guys with both business know. and tech.knowledge.
Think out its ur chance to make the employers beckon for you |
|
Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006 Posts: 1436 Location: Bangalore,India
|
|
|
|
Mahesh,
Quote: |
Everthing have its own pros and cons ...thats how it is. |
I really like the way you look at the things.
But, did you realise you have had answered for two and half year query? |
|
Back to top |
|
|
umakanth.ravirala
New User
Joined: 04 Sep 2007 Posts: 15 Location: Halifax, United Kingdom
|
|
|
|
Hi Mahesh,
I do accept your words, but there is another side of testing. Well let me tell you.
Assume there is a schedule which has 200 jobs(200 programs) and a developer changed 5-10 programs in the schedule to add a new business functionality. The developer changes only 5-10 programs and test it in component level.
When it comes to system testing, the tester will test all 200 jobs to see the impact of 5-10 changed programs on overall system. Here the tester got an exposure to 200 programs where as the developer got only 5-10 programs.
Do you think the tester will have less technical knowledge in this scenario?? |
|
Back to top |
|
|
umakanth.ravirala
New User
Joined: 04 Sep 2007 Posts: 15 Location: Halifax, United Kingdom
|
|
|
|
Murali,
I did not observe the date of this query man. I was just searching posts related to mainframe testing and I saw this post |
|
Back to top |
|
|
|