Some annoying things in software testing _ Software Testing

1, "Software testing too easy, who can do" view

"One of the most frustrating things about being a software tester is that you don't get the respect you deserve most of the time," said Sodhani, who works for an IT service company in Texas. "I'm surprised to see the software testing team being downsized to this point, Most of the people in the team don't have any career goals, they work just for the paycheck.

Sodhani mentions that in his career, his former colleagues chose software tests because it was the only job they could find. "For me, there is no problem with other people's career goals," he said. But the reality is frustrating, and everyone looks at you with this look, even if you're doing something worthwhile, ' What does this guy know? "He sympathizes with passionate, idealistic software testers, but" they're in the awkward position of not being concerned about their careers. "

2, running around to collect demand

Another worry for Sodhani is that in a company that practices agile development, no requirements are documented. Indeed, there is no requirement document, "Everything is verbal." I still remember how scared I was when my boss assigned me a test assignment.

The first thing he was going to study was not the application software to test, but the developers assigned to work together. "I'm relieved if I know that the developer is the one who can answer all my questions," he said. I don't care about the needs, but how to work well with the developer, because once you know the key requirements information, the necessary tests are done again.

3, the developer instructs the software Test engineer how to test

Here is a vivid example. "I'm involved in a project to test behind the scenes and need to validate some of the database tables." "Because he doesn't know the table name and structure of the database, he needs to ask the developer," he said directly, ' I'll send you some of my use cases, you just run, and that's what you need to do. ' I stood there, trying to figure out what he had just said.

Obviously, the developer told him to run the same use case in the test, as it did in the code, and the developer confirmed that this was what he meant. He said that until now, the tests on the project were limited to that. So I thought, ' What the hell am I testing? ' I looked at the same data as the unit test that the developer might have done and said ' it's great. ' But that's not what I want. "All he wants to do is to know the name of the table and their direct relationship, and then he can write his own test cases, but the developers have different ideas."

4. Salary is not equal

You should be able to recall. Cisco's Jeff Feldstein describes the salary equivalence between testers and developers as a key factor in attracting and retaining talented testers. "Based on my experience, I've found that testers and developers are not in the same category as salary standards," he said. "I never got a convincing answer when he asked the boss for a specific reason." Most of the answers are simply saying that testers do less than developers. "A typical first conclusion, then find the reason."

Sodhani uses professional sports teams as an example to compare the salary differentials in the IT department. "A sports privileged team hired a talented athlete who offered him the best contract to keep him." "Although the team has never won the championship, the talented players in the team have given everyone confidence and inspired all the athletes," he said. "The test is the same. If you have a very skilled tester, but you give him the same salary criteria as other ordinary testers, he's not getting a chance to get promoted, but you're forcing your talented tester to leave. ”

5, too concentrated in manual testing

S0sodhani said: "Manual testing does not require too many skills, as long as you actively willing to work, the courage to destroy, you can do well." But, he explains, with his two previous jobs, that some knowledge--here with test automation Examples--will help testers achieve their goals.

"In Job A, I'm a stress test engineer, and a manager is an expert on the automation tools I'm working with." He knew what I was talking about, we often had heated technical discussions, and I learned a lot from it. In job B, members of my team have little background in automated testing and have little interest in learning new things. We never put our energies into automation, so that it has been postponed. "He was very frustrated because no one discussed technology with him. "Everyone talks about family chores," he said. "This highly repetitive, stalled manual testing effort" has made me realize how important team members are to their job satisfaction. ”

This article is reproduced from the 51Testing Software test network, see more: http://www.51testing.com/html/news.html