Not many Salesforce people on here yet, I guess. I found a solution, I don’t know why it works, but it works. All parts of the test that access normal objects need to be wrapped in a System.runAs that explicitly uses the current user, like this: User thisUser = [ select Id from User where … Read more
Try using the metaobject. pWin->metaObject()->className();
I had a similar problem. The solution was the method Once() In your mock add an .Once() and repeat the mock with each result you need. Something like this: lib.Mock.On(“method”, arg).Return(test.mockError).Once() lib.Mock.On(“method”, arg).Return(nil).Once() Each mock result will be returned only once. https://godoc.org/github.com/stretchr/testify/mock#Call.Once
In a sentence: Code coverage tells you what you definitely haven’t tested, not what you have. Part of building a valuable unit test suite is finding the most important, high-risk code and asking hard questions of it. You want to make sure the tough stuff works as a priority. Coverage figures have no notion of … Read more
My reference is alway Structure of a Haskell project and How to write a Haskell program which spell out some defaults which the community more or less seems to follow. It has worked well for me so far but my projects have not been very large as of yet. What is suggested in Structure of … Read more
I’m adding another answer since I’ve just found this approach that in my opinion is easier and really simple to read and use. I’ve created a dummy Alamofire class that contains only the functions and the types necessary for tests. Now I include this file in the test target instead of the real Alamofire. For … Read more
I favour keeping unit-tests in separate source files in the same directory as production code (#3). Unit tests are not second-class citizens, their code must maintained and refactored just like production code. If you keep your unit tests in a separate directory, the next developer to change your production code may miss that there are … Read more
It turns out that one can right-click on the source code of any of: A specific test (public void MyTest()) A class containing tests (public class MyTestClass) A namespace containing tests (namespace My.Project.Test) and get a context menu to either run or debug tests within each given scope. (Note: Text in Context Menu does not … Read more
When you call add_test(…), CMake will not generate the tests unless enable_testing() has been called. Note that you usually don’t need to call this directly. Just include(CTest) and it will invoke it for you. My CMake setup often looks like this: include(CTest) # note: this adds a BUILD_TESTING which defaults to ON # … if(BUILD_TESTING) … Read more
Here’s an article on test categorization with some arguments I won’t mention the benefits of testing as a whole, once we’re just comparing unit tests vs. functional tests: Unit testing helps you reduce the scope where to look when there’s an error. – Let’s include classes C, D, E, …, Z in this scenario. If … Read more