What does a software testing consultant do??

Watch
Sam89
Badges: 4
Rep:
?
#1
Report Thread starter 9 years ago
#1
Hi all,

Here's the story, I've accepted a job offer with the title testing consultant and now im kind of worried, my degree was in information systems, I hardly ever did programming and when I did I was never good at it although I do want to develop my technical skills, this is a graduate role....what can I expect?? The role advertised in the website doesn't really specify what I'm going to do...all it says is I'll learn different testing methodologies and work alongside professionals? :confused:

I'm really nervous, I start in a few weeks, I really want to do well (btw I made it clear at the interview that I didn't have many technical skills it was all theory) but I would prefer no programming.

Any advice would be appreciated, this is my first full time job, which is why I'm so nervous, and the fact that I'll be on probation period the first 3-6 months doesn't help : $
0
reply
kingkhan
Badges: 0
Rep:
?
#2
Report 9 years ago
#2
Common responsibilities of a Software Test Lead include the ones given below.
1. Be updated on the latest testing techniques, strategies, testing tools/ test frameworks and so on
2. Be aware of the current and upcoming projects in the organization
3. Review and analyze the project requirements
4. Plan and organize the knowledge transfer to the Software Test Engineers and self
5. Collect the queries related to the requirements and get them resolved by the business person (e.g. the client, business analyst, product manager or project manager) assigned to the project
6. Plan, organize and lead the testing kick-off meeting
7. Scope the required tests
8. Design the required test strategy in line with the scope and organization standards
9. Create the software test plan, get it reviewed and approved/ signed-off by the relevant stakeholders
10. Evaluate and identify the required test automation and test management tools
11. Estimate the test effort and team (size, skills, attitude and schedule)
12. Create the test schedule (tasks, dependencies and assigned team members)
13. Identify the training requirements of the Software Test Engineers
14. Identify any test metrics to be gathered
15. Communicate with the client or on site/ offshore team members, as required
16. Review the test cases and test data generated by the Software Test Engineers and get them to address the review comments
17. Track the new/ updated requirements in the project and modify testing artifacts accordingly
18. Determine, procure, control, maintain and optimize the test environment (hardware, software and network)
19. Get information on the latest releases/ builds from the development team/ the client
20. Create and maintain the required test automation framework(s)
21. Administer the project in the test management system
22. Administer the Application under test (e.g. add users for the tests), as required
23. Assign tasks to the Software Test Engineers based on the software test plan
24. Check the status of each assigned task daily and resolve any issues faced by the team members with their tasks
25. Ensure that each team member is optimally occupied with work (i.e. each Software Test Engineer should not be too overloaded or too idle)
26. Re-assign the testing tasks, as required
27. Track the assigned tasks with respect to the software test plan and the project schedule
28. Review the test automation created by the Software Test Engineers and get them to address the review comments
29. Own and maintain the test automation suite of the project
30. Schedule and execute the test automation on the project
31. Review defect reports and assign valid defects to the relevant developer/ development manager
32. Assign returned defect reports and assist the concerned Software Test Engineer, as required
33. Ensure the resolved defects are re-tested
34. Consolidate and report test results to the concerned stakeholders
35. Be approachable and available to the Software Test Engineers, as required by them
36. Update the software test plan, as required
37. Ensure that the test cases are updated by the Software Test Engineers, as required
38. Ensure that the test automation is updated based on the updated test cases
39. Gather the decided test metrics
40. Escalate and obtain resolution of the issues related to the test environment and team
41. Plan, organize and lead team meetings and ensure action is taken based on the team discussions
42. Plan and organize training for the Software Test Engineers
43. Review the status reports of the Software Test Engineers
44. Review the time logged by the Software Test Engineers for various activities
45. Report the status to the stakeholders (e.g. the client, project manager/ test manager and the management)
46. Keep the Software Test Engineers motivated
47. Improve the test process based on the suggestions by others and own judgment
48. Manage own energy level and time
4
reply
Sam89
Badges: 4
Rep:
?
#3
Report Thread starter 9 years ago
#3
Wow thanks for that list! Although I think I'll only be going a fraction of that since it a trainee role.
0
reply
Sam89
Badges: 4
Rep:
?
#4
Report Thread starter 9 years ago
#4
(Original post by kingkhan)
Common responsibilities of a Software Test Lead include the ones given below.
1. Be updated on the latest testing techniques, strategies, testing tools/ test frameworks and so on
2. Be aware of the current and upcoming projects in the organization
3. Review and analyze the project requirements
4. Plan and organize the knowledge transfer to the
Software Test Engineers and self
5. Collect the queries related to the requirements and get them resolved by the business person (e.g. the client,
business analyst, product manager or project manager)
assigned to the project
6. Plan, organize and lead the testing kick-off meeting
7. Scope the required tests
8. Design the required test strategy in line with the scope
and organization standards
9. Create the software test plan, get it reviewed and
approved/ signed-off by the relevant stakeholders
10. Evaluate and identify the required test automation and test management tools
11. Estimate the test effort and team (size, skills, attitude and schedule)
12. Create the test schedule (tasks, dependencies and assigned team members)
13. Identify the training requirements of the Software Test Engineers
14. Identify any test metrics to be gathered
15. Communicate with the client or on site/ offshore team members, as required
16. Review the test cases and test data generated by the Software Test Engineers and get them to address the review comments
17. Track the new/ updated requirements in the project and modify testing artifacts accordingly
18. Determine, procure, control, maintain and optimize the test environment (hardware, software and network)
19. Get information on the latest releases/ builds from the development team/ the client
20. Create and maintain the required test automation framework(s)
21. Administer the project in the test management system
22. Administer the Application under test (e.g. add users for the tests), as required
23. Assign tasks to the Software Test Engineers based on the software test plan
24. Check the status of each assigned task daily and resolve any issues faced by the
team members with their tasks
25. Ensure that each team member is optimally occupied with work (i.e. each Software Test Engineer should not be too overloaded or too idle)
26. Re-assign the testing tasks, as required
27. Track the assigned tasks with respect to the software test plan and the project schedule
28. Review the test automation created by the Software Test Engineers and get them to address the review comments
29. Own and maintain the test automation suite of the project
30. Schedule and execute the test automation on the project
31. Review defect reports and assign valid defects to the relevant developer/ development manager
32. Assign returned defect reports and assist the concerned Software Test Engineer, as
required
33. Ensure the resolved defects are re-tested
34. Consolidate and report test results to the concerned stakeholders
35. Be approachable and available to the Software Test Engineers, as required by them
36. Update the software test plan, as required
37. Ensure that the test cases are updated by the Software Test Engineers, as required
38. Ensure that the test automation is updated based on the updated test cases
39. Gather the decided test metrics
40. Escalate and obtain resolution of the issues related to the test environment and team
41. Plan, organize and lead team meetings and ensure action is taken based on the
team discussions
42. Plan and organize training for the Software Test Engineers
43. Review the status reports of the Software Test Engineers
44. Review the time logged by the Software Test Engineers for various activities
45. Report the status to the stakeholders (e.g. the client, project manager/ test manager and the management)
46. Keep the Software Test Engineers motivated
47. Improve the test process based on the suggestions by others and own judgment
48. Manage own energy level and time

(Original post by HarrisonJSmith)
Sounds like Alpha/Beta testing of software. Finding
bugs and the like. Basically acting like a user.

Please, anyone feel free to correct me as i am no expert on the matter
Thank you two! I hope they go easy on me as it's a trainee role, and I can work towards a more senior role later!
0
reply
Delaney
Badges: 16
Rep:
?
#5
Report 9 years ago
#5
If you're a trainee, don't worry! You're primarily there to learn. Try and absorb as much information as you can and calm down You wouldn't have got the job if you didn't meet their requirements
1
reply
kingkhan
Badges: 0
Rep:
?
#6
Report 9 years ago
#6
glad to help you
0
reply
Sam89
Badges: 4
Rep:
?
#7
Report Thread starter 9 years ago
#7
(Original post by Delaney)
If you're a trainee, don't worry! You're primarily there to learn. Try and absorb as much information as you can and calm down You wouldn't have got the job if you didn't meet their requirements
Thanks lol, I really need to chill out. Its a graduate role the title is trainee consultant, and you're right, I dunno why I'm panicking, maybe it's because many people at the interview had previous experience and technical skills, yet they didn't get selected and I did, I'm just doubting myself.
1
reply
n65uk
Badges: 13
Rep:
?
#8
Report 9 years ago
#8
I started in a software testing role and am now a developer, it is a great role to find your feet in computing/IT because it can encompass a lot of different aspects, for example:

Programming: if you are interested and have access to the code, you can debug the issues you find and get a general feel of the program, really is a great way to figure out how the code works, how the program fits together, and what common ways you can use to fix bugs.

User experience: Part of testing is thinking about whether it could be easily used by a user. Testing is a "what if" job. Never assume anything whilst in this job, if you are in doubt in how a user is going to use something, query it with the programmer.

Business: Part of testing is checking whether the finished product meets its requirements set out by the managers at business level. Is a simple thing, but it is business related. A lot of times a tester may feel that the business requirements need changing.

Support: Quite often testers are asked (not saying you will be) to provide 2nd level support to users.

Automation: Ties in with programming. If you want to, you can use your manual testing experience to dive into automation testing, using tools such as Selenium. This is purely automating the most basic testing tasks as part of the build process.

Programmers themselves: You will tend to notice common mistakes programmers make, so you can look out for these instantly
3
reply
Sam89
Badges: 4
Rep:
?
#9
Report Thread starter 9 years ago
#9
(Original post by n65uk)
I started in a software testing role and am now a developer, it is a great role to find your feet in computing/IT because it can encompass a lot of different aspects, for example:

Programming: if you are interested and have access to the code, you can debug the issues you find and get a general feel of the program, really is a great way to figure out how the code works, how the program fits together, and what common ways you can use to fix bugs.

User experience: Part of testing is thinking about whether it could be easily used by a user. Testing is a "what if" job. Never assume anything whilst in this job, if you are in doubt in how a user is going to use something, query it with the programmer.

Business: Part of testing is checking whether the finished product meets its requirements set out by the managers at business level. Is a simple thing, but it is
business related. A lot of times a tester may feel that the business requirements need changing.

Support: Quite often testers are asked (not saying you will be) to provide 2nd level support to users.

Automation: Ties in with programming. If you want to, you can use your manual testing experience to dive into automation testing, using tools such as Selenium. This is purely automating the most basic testing tasks as part of the build process.

Programmers themselves: You will tend to notice common mistakes programmers make, so you can look out for these instantly
Thank you for that! It all seems okay except for the programming part it was never my strong point! What kind of training did you receive for your tester role?
0
reply
adelitaashmi
Badges: 0
Rep:
?
#10
Report 6 years ago
#10
Exactly, when you did not have much idea about you are confused, I was too..

still it's going tough for me to what to do, I am also a graduate with CS. And because of recession in the market I am a bit nervous which should be a better career option to be chooses. Of course, playing a software engineering role is really good for those who really did not have a complete touch of programming..felt so many difficulty !

Capacity Building Programme
0
reply
chosenone93
Badges: 19
Rep:
?
#11
Report 4 years ago
#11
(Original post by Sam89)
Hi all,

Here's the story, I've accepted a job offer with the title testing consultant and now im kind of worried, my degree was in information systems, I hardly ever did programming and when I did I was never good at it although I do want to develop my technical skills, this is a graduate role....what can I expect?? The role advertised in the website doesn't really specify what I'm going to do...all it says is I'll learn different testing methodologies and work alongside professionals? :confused:

I'm really nervous, I start in a few weeks, I really want to do well (btw I made it clear at the interview that I didn't have many technical skills it was all theory) but I would prefer no programming.

Any advice would be appreciated, this is my first full time job, which is why I'm so nervous, and the fact that I'll be on probation period the first 3-6 months doesn't help : $
how did/do you find this role? would be interested to know as i have been offered a place on a testing graduate scheme
0
reply
yourdad
Badges: 0
Rep:
?
#12
Report 4 years ago
#12
making desk fans out of new shoes and brilliance
0
reply
X

Quick Reply

Attached files
Write a reply...
Reply
new posts
Back
to top
Latest
My Feed

See more of what you like on
The Student Room

You can personalise what you see on TSR. Tell us a little about yourself to get started.

Personalise

Current uni students - are you thinking of dropping out of university?

Yes, I'm seriously considering dropping out (172)
14.68%
I'm not sure (54)
4.61%
No, I'm going to stick it out for now (344)
29.35%
I have already dropped out (35)
2.99%
I'm not a current university student (567)
48.38%

Watched Threads

View All