TL;DR

As a software tester, you could be a task executor or a passionate software tester with a mission. The post is based on a remarkable book written by Chad Fowler, The Passionate Programmer.

When I started as a software tester, I was a task executor. I got a testing task, did it in my best knowledge, and did not advertise what I had done. To be a passionate software tester, you need to have some passion. My passion is context driven school of testing, I always try to do my testing aligned with that school. In the beginning, it was not so easy to do it. I was passionate, but I was not a jerk about it. If all my explanations and facts about context-driven testing failed, I did it how it was requested. But the trail for my passion was noted.

You should find your own passion. This could be unit testing with mocking. Master it, apply it, and, most importantly, learn to explain what benefits it brings to your project. This is your path to passionate software tester.