Interview question for a comp where there's no processes/no QA /SDLC setup
What should a test Engineer do in 60/90 days of hire where there's no qa/sdlc/processes setup and hes in-charge of setting these up. What specific tools and knowledge one should need to accomplish this.
I came up with below points so far.
I'd really appreciate any inputs on "how" part and on any other points we need to add here.
1)Learn the business.
2)Learn the system.
3)Determine how many environments we would need. how?
4) Determine sdlc methodolgy we would need. how?
5) Determine server needs for environments. how?
6) Determining tools. how?
Thanks a lot
I think one of the key things you want to establish early is
Originally Posted by neeshpal
- Change control process- Without good change control, it'ls hard to know what's delivered, what you need to test, and what's considered fully tested. Without change control, you're going to go through this hoop jumping dog show of full regression on any sort of change.
- Establish software metrics around bugs and tests. I'd probably would recommend a getting a TCM system setup.
- Establish a release flow. Dev > QA > Staging > Release, etc...
After setting up the important items that you and David mention, I like the format of ALM. I would start by adding new requirements. Writing manual scripts linking them in ALM. I would do this for one build and see how it works. I have said a combination of these things on an interview and it went OK.
They don't have to use ALM, but anohter tool that holds the QA pieces together. I am seeing them on the shareware side also.
Thank you both for your replies
Tags for this Thread