Technical requirements
Test data needs to be saved, archived, loaded, version controlled, and so on. That, in a way, makes it very much like code. Our goal with this chapter is to aid the communication between programmers and less technical staff. Specifically, a tester who does not program might be able to create technical requirements for the test data that a product owner could prioritize as a feature for ongoing development. You’ll also learn how to articulate the cost in terms of time investment if those tools don’t exist. Programmers who read this chapter will understand the ideas and immediately be able to implement them.
The solutions in the chapter will tend to be high-level, programming-language-agnostic concepts. So, no specific programming language is required. An understanding of databases and SQL will be helpful. Teams that use key/value pairs and NoSQL databases will also be able to benefit from this chapter.
