Skip to content

Test/proceed test#377

Open
celikerde wants to merge 8 commits into
devfrom
test/proceed-test
Open

Test/proceed test#377
celikerde wants to merge 8 commits into
devfrom
test/proceed-test

Conversation

@celikerde

@celikerde celikerde commented Jun 22, 2026

Copy link
Copy Markdown
Collaborator

Checklist

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Types of changes

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to our CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

Description

Related Issue

- Implement tests to verify deletion of status file on reset.
- Ensure route statuses are cleared and treated as inactive after reset.
- Confirm no failure occurs when resetting without an existing status file.
- Introduced tests for AssignmentStatus, PaymentStatus, Permission, ProcessStatus, and RevisionStatus enums.
- Verified expected values, labels, colors, icons, and additional methods for each enum.
- Ensured comprehensive coverage of enum functionalities to maintain code integrity.
- Introduced tests for ModularousUserRegistered, ModularousUserRegistering, ModularousUserVerification, and VerifiedEmailRegister events.
- Verified constructor behavior, request handling, and OAuth status for each event.
- Ensured event instances are independent and utilize the SerializesModels trait for model serialization.
- Introduced tests for the authentication handler to verify behavior when a user is already authenticated, when authentication throws an exception, and when session lookup fails.
- Added tests for the ValidationException class to ensure correct JSON response formatting and error handling.
- Ensured comprehensive coverage of both the handler and exception functionalities to maintain code integrity.
- Introduced comprehensive tests for the HasPriceableMutators trait, ensuring correct behavior of price-related attributes and methods.
- Verified that the trait is properly used by the model and that default values are returned when no base price is set.
- Included tests for formatted attributes to ensure they utilize the PriceService correctly with currency formatting.
- Ensured coverage of scenarios involving discounts and VAT calculations to maintain code integrity.
- Introduced tests for the CacheObserver to ensure cache invalidation occurs correctly on model events: created, updated, deleted, restored, and forceDeleted.
- Verified that caching behavior is properly handled when caching is enabled for the model's module.
- Ensured comprehensive coverage of cache invalidation scenarios to maintain code integrity.
- Introduced comprehensive tests for the PriceableObserver to validate the correct handling of price calculations, including raw amounts and VAT amounts based on configuration settings for including or excluding VAT.
- Verified behavior for various scenarios, including zero price values and discount percentages, ensuring accurate attribute management during model events.
- Ensured thorough coverage of the saving, retrieved, and replicating methods to maintain code integrity.
@oguzhanbukcuoglu
oguzhanbukcuoglu changed the base branch from 12.x to dev June 27, 2026 11:41

@oguzhanbukcuoglu oguzhanbukcuoglu left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You recreated some tests, go over tests/Models folder. There are also same test classes under the folder.

@celikerde

Copy link
Copy Markdown
Collaborator Author

You recreated some tests, go over tests/Models folder. There are also same test classes under the folder.

I will check and fix it within today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants