Defining the whole (complete) process of testing
A week ago I got my first job in a company as a QA specialist and I have a task to think off and define the complete testing processes which will be formalized and will be used further in that company (tools, techniques, types of tests...).
The company creates .Net applications and it did not have a separate department for testing, which means that I have no help in my work and the problem is that I am a beginner in this field.
So I'd ask all the experienced testers to describe briefly what should I include in my work, in my documentation and how should I perform the flow of the whole testing process. For now, from my research I decided to use Selenium for functional testing and Jmeter for load testing.
Maybe this is not a regular question, I just need a kind of conversation with experienced people in this field. Thank you very much.
Re: Defining the whole (complete) process of testing
If they put a complete beginner in charge of creating a testing process, then their expectations aren't very high.
Not trying to be harsh here, just trying to tell you not to be very worried.
This might help - it's a checklist I wrote last time I was faced with starting up a new QA department: