unit-testing

问题 I am having issue with Mocking a JDBC call using the MockitoJUnitRunner. Somehow Mockito is not mocking the actual call even though I have below subbing line into the test class. when(readOnlyJdbcTemplate.query(anyString(), any(Object[].class), any(int[].class), any(FeatureCollectionResponseExtractor.class))).thenReturn(actual); Very similar mocking is working in another class for very similar type of method. The only difference between them is my other class does have 3 parameters instead of

问题 As can be seen in AndroidX Test 1.3.0 alpha04 release notes: Include the test storage service in the test services Unfortunately, this makes standard connectedDebugAndroidTest to fail because this screen is getting displayed: Choose what to allow TestServices to access And this requires my interaction in order to proceed with UI testing. This makes me to hang with already quite old 1.3.0-alpha03 artifacts, although 1.3.0-beta01 is already available. Question: How to accepts this permission

问题 I'm building some unit tests for my Python module which interfaces with a MySQL database via SQLAlchemy. From reading around I gather the best way to do this is to create a test database that I can query as if it was the real thing. I've done this however how should I test the existing queries in the module as they currently all point at the live database? The only idea I'd come up with was to do something like the following: def run_query(engine, db_name='live_db') engine.execute(f'SELECT *

问题 I'm having trouble writing tests around a factory that uses Autofac keyed registrations. In an Autofac module, I register things like this: builder.RegisterType<TypeAMessageHandler>().As<IMessageHandler>() .Keyed<IMessageHandler>(MessageTypeEnum.A); builder.RegisterType<TypeBMessageHandler>().As<IMessageHandler>() .Keyed<IMessageHandler>(MessageTypeEnum.B); builder.RegisterType<MessageHandlerFactory().As<IMessageHandlerFactory>(); Then the constructor for the factory gets a nice Index

问题 I'm having trouble writing tests around a factory that uses Autofac keyed registrations. In an Autofac module, I register things like this: builder.RegisterType<TypeAMessageHandler>().As<IMessageHandler>() .Keyed<IMessageHandler>(MessageTypeEnum.A); builder.RegisterType<TypeBMessageHandler>().As<IMessageHandler>() .Keyed<IMessageHandler>(MessageTypeEnum.B); builder.RegisterType<MessageHandlerFactory().As<IMessageHandlerFactory>(); Then the constructor for the factory gets a nice Index

问题 I'm having issues with Jest testing that a closure (an inner function) has been called after calling the outer function. I've tried using the spyOn with no positive result. This seems to be a relatively simple problem, to which I haven't found any results from googling. // helper.js export const bar = () => {} export const foo = () => { bar(); //How do I test that this has been called? } //helper.test.js import * as H from 'helper'; const barSpy = jest.spyOn(H, 'bar'); H.foo(); expect(barSpy)

问题 I'm having issues with Jest testing that a closure (an inner function) has been called after calling the outer function. I've tried using the spyOn with no positive result. This seems to be a relatively simple problem, to which I haven't found any results from googling. // helper.js export const bar = () => {} export const foo = () => { bar(); //How do I test that this has been called? } //helper.test.js import * as H from 'helper'; const barSpy = jest.spyOn(H, 'bar'); H.foo(); expect(barSpy)

问题 I made a class with private name, units sold, and units remaining. I made two class methods that return, units sold and units remaining as ints. I want to sort the units sold from greatest to least, but I get errors as I explain in the comments. What am I doing wrong, is it something very obvious? #include <iostream> #include <string> #include <fstream> using namespace std; const int MAX_SIZE = 1000; const char FILE_NAME[14] = "inventory.txt"; //make an Item class class Item { private: string

问题 I am planning to use Moq for unit testing my azure service fabric application. I saw some of the examples here https://github.com/Azure-Samples/service-fabric-dotnet-web-reference-app/blob/master/ReferenceApp/Inventory.UnitTests/InventoryServiceTests.cs. The test I saw seems like actually writing to reliable dictionary and not mocking. Is there way to mock the add/remove from reliable dictionary? How do I unit test something like below public async Task<bool> AddItem(MyItem item) { var items

问题 I am trying to find out how to run a test on a function which grabs a variable value from session['user_id'] . This is the specific test method: def test_myProfile_page(self): with app.test_client() as c: with c.session_transaction() as sess: sess['user_id'] = '1' rv = c.get('/myProfile') assert 'My Profile' in rv.data This is the view being tested: @app.route('/myProfile') def myProfile(): if not session.get('logged_in'): return render_template('login.html') else: profileID = session['user