Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have a set of Visual Studio Team System unit (integration really) tests that talk to a remote database. The tests are getting too slow and unwieldy. I'd like to replace the entire set of tests with mocked out versions. The problem is it's painful to write all the expect statements that mimic what an entire database does.
Does anyone know of a tool or add-on that will run an existing test, figure out what the non-mocked version actually returns and write out the Expect.Call's to duplicate the functionality? I know this is a long shot, but I feel like it should be possible.
Ok, I ended up writing it myself. Here is the blog post overview:
Write My Rhino Mocks Expect Statement
And here is the CodePlex project:
WriteMyExpectStatement
Hope this helps someone somewhere.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
In the karate project I am trying I have used karate's ability to assert database entries. And I was looking for a way to insert SQL scripts as a 'given' inside the test rather than calling a java class. Did not see any example in the demo project of karate.
What would be the ideal way to do this?
If you have already seen the JDBC demo and still feel that is too complicated, then I'm sorry - look for another framework :)
Also see this example if it helps: https://twitter.com/KarateDSL/status/1144458169822806016
And the whole Given When Then approach is over-rated, see: https://stackoverflow.com/a/47799207/143475
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
How would i go about making a game engine from scratch, i know that this is a very hard task and the final engine will not be able to compete with an engine like Unreal or Unity.
I only plan to use this to get better at programming and if it helps i'm using C#.
Check: http://www.gamefromscratch.com/post/2013/06/14/A-tutorial-series-on-building-a-game-engine-from-scratch-almost-literally.aspx
You may also want to check more interactive tutorials such as those on
Udemy, which cost some money but offer a much more interactive environment. I'm sure you will be able to find a C# game engine guide on there.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
While using Gitflow, what is the reason for separating branch naming to feature vs bugfix vs hotfix?
I.e. why not just, for example, instead of:
feature/
bugfix/
hotfix/
Just do:
change/
What does separating by feature/bugfix/hotfix buy?
Great questions and the answer really depends on how you sort your git. The branching model and gitflow in general is trying to give us some order in the chaos that commits are just after a couple of days.
The image below shows you what they though makes most sense.
(As far as I know it all came from this blog post by Vincent Driessen)
Separating your hotfixes which merge directly into master and your bugfixes which merge into dev makes it easier to go with your product cycle.
The idea is you build your app, create features, make a release candidate (beta test) and then release your app. Hotfixs can be necessary at any time after this. No point in going back all the way to the feature branch and issuing a bug fix there as the feature may already been developed further.
Does that make sense?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I have phased out a few classes from a project and removed all references to them. Is it better practice to make them obsolete or delete them from the project?
I am a sole developer of this system. I have spent some time Googling this and I have also looked at a few articles on MSDN. However, I cannot find the answer to my specific question.
If nobody else is using your system it is redundant to keep this classes/methods.
Deprecating classes/methods is usefull if you got some clients of your code and you do not want to make their code crash. You are deprecating classes/methods then to indicate that new users should use something else.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Is it normal to include the source for a testing framework in the tested application's repository.
For example, a C++ application tested with googletest. Does googletest code go in my repo? If so how do I handle building. Do I have my makefile call googletest's makefile?
Alternatively, should I ask the end user to provide an environment variable pointing to googletest if they want to run the tests?
Typically all your tests will be in a separate repository, I know for us we have all of our integration tests in a different repository but keep unit tests local.
Do you really want your clients to see all your test cases? Do the tests really need to be run on client machines? These are questions you have to ask yourself. Then you will have your answer