What are some of the challenges you run into in the day to day? Any common themes you have seen in your career that made testing harder than it had to be?
Software Manager, Agile Aficionado, Tech Dabbler, and Public Speaker. A lifelong learner, the prospect of something new and coffee are what get me up in the morning.
Most have been in regards to the framework choices and being able to handle new functionality when the product has changed. It's made me focus on open frameworks that can support multiple languages, especially when trying to deal with testing front and back ends. UI testing and backend (API or Database) are different and sometimes require different types of tests.
As to common themes what I tend to do over and over is try to teach people how best to handle testing outside of their own functional area. Its easy to write tests for a method when its used in one area, common libraries are harder and require additional thought and planning. I tend to learn towards a "teach you how to test" rather than write specific tests, having philosophical discussions on test strategy with developers - sometimes shallow ones to get them on board and with others in depth. It depends on the person, but I try to leave the environment better than when I found it.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
What are some of the challenges you run into in the day to day? Any common themes you have seen in your career that made testing harder than it had to be?
Most have been in regards to the framework choices and being able to handle new functionality when the product has changed. It's made me focus on open frameworks that can support multiple languages, especially when trying to deal with testing front and back ends. UI testing and backend (API or Database) are different and sometimes require different types of tests.
As to common themes what I tend to do over and over is try to teach people how best to handle testing outside of their own functional area. Its easy to write tests for a method when its used in one area, common libraries are harder and require additional thought and planning. I tend to learn towards a "teach you how to test" rather than write specific tests, having philosophical discussions on test strategy with developers - sometimes shallow ones to get them on board and with others in depth. It depends on the person, but I try to leave the environment better than when I found it.