I have found over the years that the test “role” has never meant only test. If I needed to execute something but could not due to the wrong certificate (for example) in the env I use, would need to
- understand what the issue is,
- where it manifests,
- find out if that location is within my reach
- if not then who owns this area
- what do I need to do to raise this to the external team
- what I could do to assist them getting my issue sorted
- could I get access and knowledge how to sort this out in future
- writing the issue up for all
- then actually creating the data, executing the test
have found a good way to understand not only the env you are testing in and the integration points but gets you building a your knowledge. You pick up so much that it seeps in.
From what you have put in your initial statement writing JS is part of your working day? what tools are you using and what methodologies are you using. Am able read code and can understand when there is an issue or area that needs to be debugged but being fluent, having something at my fingertips to put onto an automation framework/ or on a harness is where I feel I need to be.