I have been working as a QA in our 9 developer team for about a year. Had lots of 'firsts' within the year between personal and professional life. I replaced a QA who only did manual testing and unfortunately, no test cases were left for me to study, and no requirements either. All in all, I had to lean on exploratory testing.
So I have started a QA process (for me and for the team as well), built the bug process as well (they didn't have this process in place), and started to create test cases according to the developers' stories/users' stories and the product backlog items that were recorded in TFS.
They hired me to eventually help them do the automation. And now, the time has come. I have built an automation library of classes using
Selenium Webdriver. I have designed my tests using Page Object Model. Then I presented the sample tests to my boss. My boss asked me:
"What is the concept? If this may take time for you to create, I guess we will just move on to manual testing. I don't really get the concept."
Though he said I can continue doing my scripting while I am on my downtime since I don't have anything to test. It took me about 3 months (within those months I was also doing manual testing and at the same time learning
C# all over again since I haven't done programming in one decade). I told him this is very helpful with my regression/cross browser testing since we need to test it in Safari. But he still won't get it.
I have about 15 apps to test and counting. Since I have these apps to test one at a time, I need to execute automation testing on the side while manually testing the new features of the other app. He said, "I still don't get it". I felt disappointed and somewhat demotivated with the automation testing I should be doing but at the same time, I need to move on.
My question is how do I convince someone who doesn't have any idea of how automation tests work and how helpful this is to an organization?