Hi, in the documentation I think we should list the different options, the one in the link seems good to me.
I think you need at least a test that checks that the String in the configuration is converted into the right WriteConcern constant, a test that checks that the value is set in the driver and one that checks that the default is set when nothing is selected. I would be prone not to repeat all the "classic" test for the different configurations, the only difference seems to be which exceptions are thrown and warranties about when the message is written and they are implementation details of the driver. Davide On Fri, Feb 22, 2013 at 9:59 AM, Guillaume SCHEIBEL <guillaume.schei...@gmail.com> wrote: > Hello guys, > > I was wondering do we need to test all the new writeconcern settings ? > If the answer is yes, do we test all values with all "classic" tests like > we did for the association strategies or we just check that the value is > properly set as in DatastoreInitializationTest. > > Second question, for the doc we have 2 options: > - the first is to put all possible values into the configuration properties > table (see here https://gist.github.com/gscheibel/5012033). > > - the second is to add another section and a link into the properties table > > WDYT ? > > Have a nice day > Guillaume > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
