I have started a position in the last month where I was recruited for my knowledge in developing integrated systems in a software context. Think building lab information systems and ETL pipelines, things like that. These were mostly for small-to-medium-size companies (<$10M market cap). Just to make my current skillset clear, I've been writing software/scripts in these and other contexts as a main job function for about ten years.
My current employer has identified a need to have end-to-end testing implemented to bridge development efforts across various parts of the company. This is a company for which software has traditionally been a means to an end, but is now becoming a much more-critical part of overall revenue. This is a large company (on the order of 1,000 employees).
Put another way, there are development teams for various major components, and these teams do not currently communicate effectively. Team B might use Team A's product, but problems with Team A's work currently manifest late in Team B's development process, causing delays and issues post-release.
It is looking like I'm being selected as one of those to lead the effort to remedy this issue. At the executive level, the consensus is a need for end-to-end testing, and I think that's reasonable, though there may be other facets to an effective approach. I'd like to get an idea for how these issues are currently handled. Does anyone have recommendations for reading to supplement my research? Thanks in advance!
