integration-testing

问题 I am a bit stumped. I have the following integration test: require "spec_helper" describe "/foods", :type => :api do include Rack::Test::Methods let(:current_user) { create_user! } let(:host) { "http://www.example.com" } before do login(current_user) @food = FactoryGirl.create_list(:food, 10, :user => current_user) end context "viewing all foods owned by user" do it "as JSON" do get "/foods", :format => :json foods_json = current_user.foods.to_json last_response.body.should eql(foods_json)

问题 I am trying to execute the following scenario using maven : pre-integration-phase : Start a java based application using a main class (using exec-maven-plugin) integration-phase : Run the integration test cases (using maven-failsafe-plugin) post-integration-phase: Stop the application gracefully (using exec-maven-plugin) Here is pom.xml snip: <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.2.1</version> <executions> <execution> <id

问题 We have a Fluent NHibernate mapping test that is passing on our local machines, but when we check in to TFS, the tests are failing on the build server. We are using MSTest. The error we get is: NHibernate.Bytecode.UnableToLoadProxyFactoryFactoryException: Unable to load type 'NHibernate.ByteCode.Castle.ProxyFactoryFactory, NHibernate.ByteCode.Castle' during configuration of proxy factory class. Possible causes are: - The NHibernate.Bytecode provider assembly was not deployed. - The typeName

问题 we have quite a lot of RPG-programs here, and we do a lot of automated testing, but we are not very good yet in combining those two. Are there good ways to do automated testing on RPG programs -- or on any other ILE programs for that matter? I am aware of a project named RPGUnit, but that has it's last update in 2007. However, it seems it is still used, since RPG Next Gen is currently putting some work in including it. What's you experience with those? Is there something else, that I am

问题 I need some advice about efficient way of writing integration tests for our current ASP.NET MVC application. Our architecture consists of: A Service Layer below Controllers Service Layer uses Repositories and Message Queue (sometimes) to send messages to external applications. What I think should be done is to: Write behavioral unit tests for all pieces in isolation. So, for example, we should unit test the Service Layer while mocking Repositories and Message Queues. Same goes for Controllers

问题 I'm following this tutorial Integration Testing with Entity Framework Core and SQL Server My code looks like this Integration Test Class public class ControllerRequestsShould : IDisposable { private readonly TestServer _server; private readonly HttpClient _client; private readonly YourContext _context; public ControllerRequestsShould() { // Arrange var serviceProvider = new ServiceCollection() .AddEntityFrameworkSqlServer() .BuildServiceProvider(); var builder = new DbContextOptionsBuilder

问题 I am introducing automated integration testing to a mature application that until now has only been manually tested. The app is Windows based and talks to a MySQL database. What is the best way (including details of any tools recommended) to keep tests independent of each other in terms of the database transactions that will occur? (Modifications to the app source for this particular purpose are not an option.) 回答1: How are you verifying the results? If you need to query the DB (and it sounds

问题 I find the concept of 'integration testing' confusing. There seems to be quite a few explanations and scopes: Functional/acceptance testing (e.g. testing the user interface with for example, Selenium) Testing the integration of different classes/modules of software together (simply testing two or more classes together, without them doing anything special like db calls and stuff) Testing the system configuration function/feature-independently (database integration works, dependencies are

问题 this is regarding Espresso. I am successfully running integration test on a simulator. I think some tests are failing because it's running too fast. Is there a way to slowdown the execution/playback speeD? 回答1: It's impossible that a test fails cause to speed. Espresso can synchronize all test operations with the application under test. By default, Espresso waits for UI events in the current message queue to process and default AsyncTasks to complete before it moves on to the next test

问题 I am trying to integration test an ItemReader - here is the class: @Slf4j public class StudioReader implements ItemReader<List<Studio>> { @Setter private zoneDao zoneDao; @Getter @Setter private BatchContext context; private AreaApi areaApi = new AreaApi(); public List<Studio> read() throws Exception { return areaApi.getStudioLocations(); } Here is my bean.xml: <bean class="org.springframework.batch.core.scope.StepScope" /> <bean id="ItemReader" class="com.sync.studio.reader.StudioReader"