Run integration unit test without SQL server

Question

0.00/5 (No votes)

See more:

I have got many integration unit test in my solution. I need to run those on a build server in TFS. But the build server doesn't have SQL server installed in it and also the business is not ready to install it due to license cost.

Is there any other SDK or components that can be installed instead of SQL server so that I can get the integration test run successfully.

What I have tried:

For now we are skipping the integration test on the build but we need that also to run on our TFS build.

Posted 4-Feb-19 5:33am

Member 14129661

Updated 4-Feb-19 5:44am

Add a Solution

Comments

F-ES Sitecore 4-Feb-19 11:52am

If these are integration tests then you have to have access to SQL otherwise they're useless tests. Integration tests are to ensure your system flows end-to-end.

If these are unit tests then they shouldn't need SQL Server and if they do you haven't written them correctly and the problem you're facing now is exactly why unit tests shouldn't need access to external resources.

[no name] 4-Feb-19 11:56am

"otherwise they're useless tests", so true!

Member 14129661 5-Feb-19 3:39am

ya I know they are useless. I am helpless on it as the organisation where I am working, is not ready to pay for a proper license for the SQL server but still they want the integration testing to run on the build servers.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2019-02-04T05:45:00

Solution 1

Well ... SQL Server 2017 Express Edition | Microsoft[^] - it's free, so no licence cost, and you should be developing against an Express version anyway. Developing / testing against the production DB server is a good recipe for "Oh f*ck" moments and production downtime while databases are restored...

Posted 4-Feb-19 5:45am

OriginalGriff

Comments

Maciej Los 4-Feb-19 13:15pm

5ed!

Member 14129661 5-Feb-19 3:37am

Thanks for the information. Unfortunately, our build server has got the professional edition of the visual studio. I am not sure whether that will support the SQL Server Enterprise edition.

OriginalGriff 5-Feb-19 3:45am

Not Enterprise - that's a license option with a cost. Express edition (free), and installed as far away from the production server as physically possible!