org.junit.Test is not in JUnit5, that class is being provided by your dependency on JUnit Vintage. JUnit Vintage includes the JUnit Vintage test engine and classes such as org.junit.Test, this allows you to run JUnit4 tests alongside JUnit5 tests. It is a back compatability measure. If you want to use only JUnit5 constructs (and leave … Read more
I am currently looking for some good options to do this as well. As a result, I came across this question, and a few other potential candidate solutions. Admittedly, I haven’t tried any of them yet, so I can’t speak to their quality, but at least they are some other avenues potentially worthy of researching. … Read more
You could use the Traits feature in mstest to accomplish this. Take a look at this blog post: https://devblogs.microsoft.com/devops/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1using-traits-in-the-unit-test-explorer/
I found a working method by declaring in the beginning of the test a global variable: global.window = { location: { pathname: null } }; and checked this variable like this: expect(global.window.location.pathname).toContain(‘/new-url’); That worked fine.
Here’s a method you can use that doesn’t require altering your non-test code. Just patch the default attributes of the fields you want to affect. For example– field = User._meta.get_field(‘timestamp’) mock_now = lambda: datetime(2010, 1, 1) with patch.object(field, ‘default’, new=mock_now): # Your code here You can write helper functions to make this less verbose. For … Read more
You could refactor MyClass so that it uses dependency injection. Instead of having it create an AnythingPerformerClass instance you could pass in an instance of the class to the constructor of MyClass like so : class MyClass { private final AnythingPerformerClass clazz; MyClass(AnythingPerformerClass clazz) { this.clazz = clazz; } public boolean performAnything() { return clazz.doSomething(); … Read more
This post demonstrates how to configure this: http://atombrenner.blogspot.com/2010/07/how-to-change-resharper-naming-style.html UPDATE: The Machine.Specifications testing framework extends ReSharper to allow for custom naming styles for the tests/specs. Very cool; wish other frameworks did likewise. http://lostechies.com/derekgreer/2010/02/11/resharper-naming-style-for-machine-specifications/
You can’t mock a function’s local variable. To make your code easier to test, change it to, e.g: def keep_trying(self, timeout=300): end_time = time.time() + timeout # etc, as above so it becomes trivial for tests to run it with a shorter timeout!