On Mon, Mar 8, 2010 at 1:59 PM, Naftoli Gugenheim <[email protected]>wrote:
> Currently what I did is combine ItemListSpecs with another test, so I gave > it a more generic name than ItemsList, hence MapperSpecs2. The idea is that > some tests really have zero to do with the vendor, but higher-level > behavior. H2MemoryProvider is incidental--in memory databases are perfect > for testing. So I'd prefer not putting the choice of testing db in the name > of a driver-independent test. > If an ORM is a form of caching then these are cache-related specs. > If David vetoes the change on RB, a name is irrelevant; and depending on > his proposal it may be temporary; but I'm looking for a name that says "More > Mapper Specs except these specs are run on one arbitrary driver rather than > on all of them, because these specs are driver-independent by definition." > I'm curious how my naming proposal doesn't do that? In a much more structured way? -- James A Barrows -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
