Re: [dotNetRDF-Develop] TeamCity for dotNetRDF revisit

[Rob V. <rv...@do...>]

Tom

The style of test naming was chosen originally because when sorting tests
by name it nicely groups tests so that you can run all the tests that
pertain to some area.

I would like to preserve this at least because I personally find it very
useful on a daily basis, we could try and migrate towards a compromise
style e.g

Mime - ParsingTurtleW3CBaseTurtleStyle1
Yours - ShouldSuccessfullyParseValidW3CBaseTurtleStyle
Compromise - ParsingTurtleW3CAcceptsValidTurtleStyleBaseDeclaration

(This is not a great example because the test name already calls out a
bunch of stuff but you get the idea)

So this fulfills my usage of being able to group tests easily by name and
your aim of having more descriptive naming for diagnosing what failed,
what do you think?

Rob

On 4/13/13 9:08 AM, "Tomasz Pluskiewicz" <tom...@gm...>
wrote:

>Hi again Rob
>
>There is one more thing about unit tests. I have noticed that you
>commonly use a same name for multiple tests and just append a number.
>It would be much more helpful if they had meaningful names so that
>when one fails it is instantly obvious why. For example
>ParsingTurtleW3CBaseTurtleStyle1 would become
>ShouldSuccessfullyParseValidW3CBaseTurtleStyle. Similarily
>ParsingTurtleW3CBaseTurtleStyle2 would become
>ShouldThrowWhenBaseDirectiveIsMissingDot and so on.
>
>Would you be okay with me gradually renaming any tests I think can
>have a better name?
>
>Thanks,
>Tom
>
>On Sat, Apr 13, 2013 at 12:23 PM, Tomasz Pluskiewicz
><tom...@gm...> wrote:
>> Hi Rob
>>
>> Some time we discussed setting up continous integration for dotNetRDF.
>> I am upgrading my VPS to a more powerful machine and I have already
>> set up TeamCity. It will also be possible to install some triplestores
>> for integration testing.
>>
>> However I'm hitting a wall with unit tests because you use MSTest.
>> Would you be fine with me converting to NUnit? That way TeamCity will
>> run without installing Visual Studio and VS Express users will also be
>> able to build the whole solution. Also I think we could ask JetBrains
>> for ReSharper licence for our project (in case you would ask about
>> running the test suite from within VS). Oh and by the way, with the
>> introduction of NUnit there can be a lot less code for similar tests,
>> which can be parametrized. I assume you know the TestCase attribute.
>>
>> When TeamCity builds are running I think we should also automate NuGet
>> publishing. For that some changes will be needed to have automatic
>> version numbering. Also you would have to explain how you nuget pack
>> dotNetRDF. In a separate email maybe.
>>
>> Also I thought that maybe there could be two flavors of those
>> packages. One as usual for stable builds and a new one, which would
>> publish automatically for each successful build. What do you think?
>>
>> A thing to consider here is moving to a dedicated branch for release
>> development and leaving default only for bugfixes.
>>
>> Any thoughs?
>>
>> Thanks
>> Tom
>
>--------------------------------------------------------------------------
>----
>Precog is a next-generation analytics platform capable of advanced
>analytics on semi-structured data. The platform includes APIs for building
>apps and a phenomenal toolset for data science. Developers can use
>our toolset for easy data analysis & visualization. Get a free account!
>http://www2.precog.com/precogplatform/slashdotnewsletter
>_______________________________________________
>dotNetRDF-develop mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop