An e-university Web Application built with ASP.NET and React.
- .NET 8.0
- Entity Framework Core
- SQL Server
- Duende Identity Server
- Mapster
- FluentValidation
- SharpGrip FluentValidation AutoValidation
- AnyAscii
- Swashbuckle
- React
- React-router-dom
- Yarn
- TailwindCSS
- Redux
- Framer motion
This application is built on a modular architecture that follows a three-layered design pattern. The architecture consists of three primary projects, each with its distinct responsibilities:
The EUniversity project serves as the Presentation Layer, responsible for the web application's user interface and interaction with users. It provides endpoints, handles HTTP requests, and encapsulates various components such as controllers. This layer delivers the user-facing experience and orchestrates user interactions.
The EUniversity.Core project represents the Business Logic Layer of the application. This layer contains the core business logic, domain models, DTOs (Data Transfer Objects), validators, and service interfaces. It defines the fundamental rules, operations, and data processing logic that drive the application's functionality.
The EUniversity.Infrastructure project serves as the Data Access Layer, housing the implementations of services, data access logic, and database-related code. It handles the technical aspects of working with databases, external services, and other infrastructure-related concerns.
Backend testing utilizes the NUnit framework in conjunction with NSubstitute for both unit and integration testing.
Integration tests are categorized into two primary groups: Controllers and Services tests. Both sets of tests make use of the WebApplicationFactory from Microsoft.AspNetCore.Mvc.Testing to facilitate testing our web application.
These tests focus on verifying the behavior and responses of endpoints within our application. They are an essential component of our quality assurance process, ensuring that our API endpoints function as expected. Our Controllers tests inherit from the ControllersTest class, which leverages the MockedProgramWebApplicationFactory. Importantly, these tests do not interact with the actual database but instead rely on mock objects to validate the behavior.
These tests are designed to assess our application's services and their interactions with the database. They are performed against a local database, ensuring that our services operate as intended when interfacing with real data. These tests are also compatible with GitHub Actions, where they take advantage of an in-memory database for faster test execution. Services tests are derived from the ServicesTest class, utilizing the ProgramWebApplicationFactory. To maintain test isolation and prevent cross-test contamination, transaction scope is used.
Username: admin
Password: Chang3M3InProduct10nPlz!
Username: student
Password: Password1!
Username: teacher
Password: Password1!
To streamline the testing and development process, our project includes a "Fake Data Generation" feature. You can generate test data by running the following command:
dotnet run --fakedata
This feature utilizes the Bogus library to create random data, ensuring that you have a realistic test environment for your application. However, please be aware that this functionality is not intended for use in production environments.
Note: Duplicate data will may be generated if test entities are removed. If the existing test data remains untouched, executing this command won't result in duplicate records, ensuring data consistency during testing. Please be aware that running this command may increase the application's launch time due to the data generation process.