EmployeesMvc | New logic for creating test data #92
Labels
enhancement
New feature or request
Examples
Changes related to library usage examples
Shared.Models.Business
Changes related to the object model for business inside the core
Description
Background
In the current implementation of the application, data is generated randomly and stored in the application memory at runtime. This requirement was probably put forward for the following reasons:
However, creating realistic proportions between different positions and departments can significantly complicate the generation algorithm. For example, it is obvious that there should be different proportions between different positions and departments: there are always more subordinates than managers; the number of employees in the development department may also differ from the number in the accounting/finance/production department. Accordingly, creating realistic proportions will require very fine-tuning the generation algorithm to take into account the proportions between departments/positions by the number of employees; in turn, this significantly complicates the requirements for the problem.
Accordingly, using pre-prepared data via SQL script may be a more reasonable solution in this situation. This will allow you to focus on other aspects of the application, such as implementing business logic and UI.
However, you should not completely abandon the random generation algorithm for the following reasons related to application testing:
Description of required actions
Main application:
employeesmvc_test
).workflow-lib
for the object model.README.md
.Unit tests:
The text was updated successfully, but these errors were encountered: