How to add "test Projects" for Unit and integration tests #10924

2 Answer(s)

• 

  0

  AI-Bot created 6 days ago

  Support Team ABP Agent

  • In ABP Studio, the “Include test projects” option exists only in the New Solution wizard. There isn’t a supported “add test projects to an existing solution” wizard/button afterward.
  • The recommended way to add tests to an existing modular monolith solution is to create the test projects manually (or scaffold a throwaway solution with tests enabled and copy the test projects into your solution).

  What to do (practical approach)

  1. Create new test projects in your existing solution (same naming convention ABP uses):

     • YourCompany.YourProject.TestBase
     • YourCompany.YourProject.Domain.Tests
     • YourCompany.YourProject.Application.Tests
     • YourCompany.YourProject.EntityFrameworkCore.Tests (or MongoDB.Tests if applicable)
     • YourCompany.YourProject.Web.Tests (if you have a Web UI / host to integration-test)

  2. Reference the right layers (typical pattern)

     • *.Domain.Tests references:
       • *.Domain
       • *.TestBase
     • *.Application.Tests references:
       • *.Application
       • *.TestBase
     • *.EntityFrameworkCore.Tests references:
       • *.EntityFrameworkCore
       • *.Application.Tests (so it can “implement” abstract tests against a real EF Core provider)
     • *.Web.Tests references:
       • *.Web (or your host/UI project)
       • *.Application.Tests
       • *.EntityFrameworkCore.Tests

  3. Follow ABP’s current recommended test structure

     • ABP’s newer approach is to keep many tests in Domain.Tests / Application.Tests as abstract base tests, then create concrete implementations in EntityFrameworkCore.Tests (or MongoDB.Tests) so tests are less coupled to the DB provider.

  References (verified)

  • https://abp.io/docs/latest/testing/unit-tests
  • https://abp.io/community/articles/4vvvp2oy

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 5 days ago

  Support Team Fullstack Developer

  Hi,

  The test projects option is only in the new solution and new module wizards. For an existing solution, you can generate the same solution again with tests in a temp folder, then copy the test project into your solution.

  1. Open your .abpsln file. Under creatingStudioConfiguration, you'll find createdAbpStudioVersion and createCommand.

  2. Install that CLI version into a separate folder, so you get the same template your solution was created from. Then run the createCommand with it in an empty folder, and add --tests --skip-initial-tasks at the end:

  dotnet tool install Volo.Abp.Studio.Cli --version <createdAbpStudioVersion> --tool-path C:\Temp\abp-cli
  mkdir C:\Temp\with-tests
  cd C:\Temp\with-tests
  C:\Temp\abp-cli\abp new YourCompany.YourProject -t app-nolayers --modern --modular ... --tests --skip-initial-tasks
  

  3. Copy the generated YourCompany.YourProject.Tests folder into your solution folder, next to the main project. Then go back to your solution folder, add it to the solution and run the tests:

  cd <your solution folder>
  dotnet sln YourCompany.YourProject.slnx add YourCompany.YourProject.Tests/YourCompany.YourProject.Tests.csproj
  dotnet test YourCompany.YourProject.Tests/YourCompany.YourProject.Tests.csproj
  

  If you've upgraded ABP or .NET since you created the solution, update the package versions and TargetFramework in the test .csproj first.

  If you have the Books sample page, Should_Create_A_Valid_Book may fail with a FOREIGN KEY constraint failed error. The test doesn't set AuthorId. Add these usings to the BookAppService_Tests file:

  using YourCompany.YourProject.Entities.Authors;
  using Volo.Abp.Domain.Repositories;
  

  And change the create part of the test like this:

  var author = await WithUnitOfWorkAsync(() => GetRequiredService<IRepository<Author, Guid>>().FirstAsync());
  
  var result = await _bookAppService.CreateAsync(
      new CreateUpdateBookDto
      {
          Name = "New test book 42",
          AuthorId = author.Id,
          Price = 10,
          PublishDate = DateTime.Now,
          Type = BookType.ScienceFiction
      }
  );
  

  Modules work the same way. With the same CLI, create a module with the same name, template and database provider in the temp solution:

  C:\Temp\abp-cli\abp new-module YourCompany.YourProject.ModuleName -t module:standard-modern -d ef -ts C:\Temp\with-tests\YourCompany.YourProject.abpsln -o C:\Temp\with-tests\modules\modulename
  

  Use -t module:ddd-modern for a DDD module, and -d mongodb if the module uses MongoDB. Then copy the test projects to the same place in your module (for a standard module it's the *.Tests folder, for a DDD module it's the whole test folder). Also copy the test entries from the temp module's .slnx and .abpmdl files into yours, and run dotnet test on the module's .slnx.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel