I'm sorry I don't have the reference in front of me but there is a paper that defines a methodlogy as consisting of a model and a set of techniques for implementing the model. I like that as a framework for discussing processes. There don't seem to be many well-known and formally defined models for testing. Most of the literature I've looked at seems to know only of the V-model. And the V-model assumes that your development model is the waterfall model so that limits its relevance. You notice this leaves a very large amount of "stuff" for the techniques part. Some random examples of what falls under techniques: a test plan template, boundary value analysis, exploratory testing, bug reporting system, code reviews, performance testing, entry and exit criteria.