I have heard from people that testing and QA are the least-sought after jobs in the software industry, they tend to be "boring" for most and freshers avoid it as much as possible. Is this true ?
My friend (from non-CS background like me) is in testing and dislikes it.
That's a subjective question. I would answer "maybe." It depends on the person. Some people find testing interesting and some find it boring. It also depends on what kind of company it is. Some define testing as executing repetative scripts (which sounds boring to me.) Some define it as writing automated scripts, doing exploratory testing to try to break the software, learning the business, etc. None of which sound boring.
I'm going to move this thread to Job Discussion where I think it will get more discussion. The questions in the Testing forum tend to be more technical in nature.
Jeanne Boyarsky wrote:
...learning the business...
What does this mean ?
Bugs will get through. No QA department is perfect. So, how to mitigate the damage? One way is to model the tests closer to the business use cases -- this way, the ones that do get through will be uncommon in production.
Jeanne Boyarsky wrote:That's a subjective question. I would answer "maybe." It depends on the person. Some people find testing interesting and some find it boring. It also depends on what kind of company it is. Some define testing as executing repetative scripts (which sounds boring to me.) Some define it as writing automated scripts, doing exploratory testing to try to break the software, learning the business, etc. None of which sound boring.
My two cents. I think too many beginners think of QA as a backup to programming. I also think two many recruiters push it as well. I think this is wrong.
IMO, QA is a specific job with specific requirements -- the requirements shouldn't be "a fresher programmer who couldn't get a programming job". Also, the job is hard enough, why stock it with people who doesn't want to be there?
Henry
Kr Manish
Ranch Hand
Joined: Jul 30, 2010
Posts: 138
posted
0
Rahul Sudip Bose wrote:I have heard from people that testing and QA are the least-sought after jobs in the software industry, they tend to be "boring" for most and freshers avoid it as much as possible. Is this true ?
My friend (from non-CS background like me) is in testing and dislikes it.
please advise.
rb
You are very true to an extent, if its in Indian service based mnc's. That is Manual Testing . That indeed IS boring and does not provide much career boost as opposed to development. On the other hand in product companies you get to do better things in testing including load/performance testing, which is very good. Also Test Automation is good. So it depends.
Having said that, in testing you have good onsite opportunities , but that depends on the organization. e.g. there are many onsite opportunities in Support projects but is even more despised than testing.
Also, you can move up the ladder in testing too, albeit little slower.
You know what I am saying ?
Misha Ver
Ranch Hand
Joined: Mar 03, 2008
Posts: 470
posted
0
Henry Wong wrote:QA's job is to find bugs -- ie. break the software.
QA's job is to prevent bugs, while Tester's job is to find bugs. Although in many companies terms "Tester" and "QA" are used interchangeably.
Mayu Mayooresan wrote:
...
I feel no passion towards QA job. Its all to do with Excel, I'm thinking of a change to Dev track. but in the other hand I'm 27 years old and if I change my track i'll spoil my 2 and half year of experience.
...
What is this Dev Track ? Is it just like preparing excel sheets or more fun and challenging ?
regards
rb.
Jimmy Clark
Ranch Hand
Joined: Apr 16, 2008
Posts: 2187
posted
1
Testing software for bugs and processing faults and testing software for "quality" are not the same things. In some cases the names of these two activities are interpretted to be the same, but they are not.
A Quality Assurance group will most likely execute their quality-oriented tests after a Testing group has released the software. For example a QA group may examine an application to determine the level of User friendliness or the User experience. Or how organized the screen layouts are and if there are too many required button-clicks, or if is friendly for those with visibility impairments. The application can still have zero bugs and zero defects and still fail QA tests.
The main purpose of a Quality Assurance group is to "assure" that software adheres to a specifed level of "quality." Entry-level staff may start here, but the organization must have senior staff managing and controlling the QA activities for it to work effectively and efficiently.
Henry Wong wrote:QA's job is to find bugs -- ie. break the software.
QA's job is to prevent bugs, while Tester's job is to find bugs. Although in many companies terms "Tester" and "QA" are used interchangeably.
I'd argue that QA's job is both to find and prevent bugs. Mainly because in in our industry, the QA team is usually responsible for both testing and QA.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.
subject: New to java - Just curious about testing and QA
0
