Privacy Policy

# Changes in PHPUnit 9.6 All notable changes of the PHPUnit 9.6 release series are documented in this file using the [Keep a CHANGELOG](https://keepachangelog.com/) principles. ## [9.6.18] - 2024-03-21 ### Changed * [#5763](https://github.com/sebastianbergmann/phpunit/issues/5763): Release nullable type changes for PHPUnit 9.6 ## [9.6.17] - 2024-02-23 ### Changed * Improve output of `--check-version` CLI option * Improve description of `--check-version` CLI option * Show help for `--manifest`, `--sbom`, and `--composer-lock` when the PHAR is used ### Fixed * [#5712](https://github.com/sebastianbergmann/phpunit/issues/5712): Update dependencies for PHAR distribution of PHPUnit 9.6 ## [9.6.16] - 2024-01-19 ### Changed * Make PHAR build reproducible (the only remaining differences were in the timestamps for the files in the PHAR) ### Fixed * [#5516](https://github.com/sebastianbergmann/phpunit/issues/5516): Assertions that use the `LogicalNot` constraint (`assertNotEquals()`, `assertStringNotContainsString()`, ...) can generate confusing failure messages * [#5666](https://github.com/sebastianbergmann/phpunit/issues/5666): `--no-extensions` CLI option does not work * [#5673](https://github.com/sebastianbergmann/phpunit/issues/5673): Confusing error message when migration of a configuration is requested that does not need to be migrated ## [9.6.15] - 2023-12-01 ### Fixed * [#5596](https://github.com/sebastianbergmann/phpunit/issues/5596): `PHPUnit\Framework\TestCase` has `@internal` annotation in PHAR ## [9.6.14] - 2023-12-01 ### Added * [#5577](https://github.com/sebastianbergmann/phpunit/issues/5577): `--composer-lock` CLI option for PHAR binary that displays the `composer.lock` used to build the PHAR ## [9.6.13] - 2023-09-19 ### Changed * The child processes used for process isolation now use temporary files to communicate their result to the parent process ## [9.6.12] - 2023-09-12 ### Changed * [#5508](https://github.com/sebastianbergmann/phpunit/pull/5508): Generate code coverage report in PHP format as first in list to avoid serializing cache data ## [9.6.11] - 2023-08-19 ### Added * [#5478](https://github.com/sebastianbergmann/phpunit/pull/5478): `assertObjectHasProperty()` and `assertObjectNotHasProperty()` ## [9.6.10] - 2023-07-10 ### Changed * [#5419](https://github.com/sebastianbergmann/phpunit/pull/5419): Allow empty `<extensions>` element in XML configuration ## [9.6.9] - 2023-06-11 ### Fixed * [#5405](https://github.com/sebastianbergmann/phpunit/issues/5405): XML configuration migration does not migrate `whitelist/file` elements * Always use `X.Y.Z` version number (and not just `X.Y`) of PHPUnit's version when checking whether a PHAR-distributed extension is compatible ## [9.6.8] - 2023-05-11 ### Fixed * [#5345](https://github.com/sebastianbergmann/phpunit/issues/5345): No stack trace shown for previous exceptions during bootstrap ## [9.6.7] - 2023-04-14 ### Fixed * Tests that have `@doesNotPerformAssertions` do not contribute to code coverage ## [9.6.6] - 2023-03-27 ### Fixed * [#5270](https://github.com/sebastianbergmann/phpunit/issues/5270): `GlobalState::getIniSettingsAsString()` generates code that triggers warnings ## [9.6.5] - 2023-03-09 ### Changed * Backported the HTML and CSS improvements made to the `--testdox-html` from PHPUnit 10 ### Fixed * [#5205](https://github.com/sebastianbergmann/phpunit/issues/5205): Wrong default value for optional parameter of `PHPUnit\Util\Test::parseTestMethodAnnotations()` causes `ReflectionException` ## [9.6.4] - 2023-02-27 ### Fixed * [#5186](https://github.com/sebastianbergmann/phpunit/issues/5186): SBOM does not validate ## [9.6.3] - 2023-02-04 ### Fixed * [#5164](https://github.com/sebastianbergmann/phpunit/issues/5164): `markTestSkipped()` not handled correctly when called in "before first test" method ## [9.6.2] - 2023-02-04 ### Fixed * [#4618](https://github.com/sebastianbergmann/phpunit/issues/4618): Support for generators in `assertCount()` etc. is not marked as deprecated in PHPUnit 9.6 ## [9.6.1] - 2023-02-03 ### Fixed * [#5073](https://github.com/sebastianbergmann/phpunit/issues/5073): `--no-extensions` CLI option only prevents extension PHARs from being loaded * [#5160](https://github.com/sebastianbergmann/phpunit/issues/5160): Deprecate `assertClassHasAttribute()`, `assertClassNotHasAttribute()`, `assertClassHasStaticAttribute()`, `assertClassNotHasStaticAttribute()`, `assertObjectHasAttribute()`, `assertObjectNotHasAttribute()`, `classHasAttribute()`, `classHasStaticAttribute()`, and `objectHasAttribute()` ## [9.6.0] - 2023-02-03 ### Changed * [#5062](https://github.com/sebastianbergmann/phpunit/issues/5062): Deprecate `expectDeprecation()`, `expectDeprecationMessage()`, `expectDeprecationMessageMatches()`, `expectError()`, `expectErrorMessage()`, `expectErrorMessageMatches()`, `expectNotice()`, `expectNoticeMessage()`, `expectNoticeMessageMatches()`, `expectWarning()`, `expectWarningMessage()`, and `expectWarningMessageMatches()` * [#5063](https://github.com/sebastianbergmann/phpunit/issues/5063): Deprecate `withConsecutive()` * [#5064](https://github.com/sebastianbergmann/phpunit/issues/5064): Deprecate `PHPUnit\Framework\TestCase::getMockClass()` * [#5132](https://github.com/sebastianbergmann/phpunit/issues/5132): Deprecate `Test` suffix for abstract test case classes [9.6.18]: https://github.com/sebastianbergmann/phpunit/compare/9.6.17...9.6.18 [9.6.17]: https://github.com/sebastianbergmann/phpunit/compare/9.6.16...9.6.17 [9.6.16]: https://github.com/sebastianbergmann/phpunit/compare/9.6.15...9.6.16 [9.6.15]: https://github.com/sebastianbergmann/phpunit/compare/9.6.14...9.6.15 [9.6.14]: https://github.com/sebastianbergmann/phpunit/compare/9.6.13...9.6.14 [9.6.13]: https://github.com/sebastianbergmann/phpunit/compare/9.6.12...9.6.13 [9.6.12]: https://github.com/sebastianbergmann/phpunit/compare/9.6.11...9.6.12 [9.6.11]: https://github.com/sebastianbergmann/phpunit/compare/9.6.10...9.6.11 [9.6.10]: https://github.com/sebastianbergmann/phpunit/compare/9.6.9...9.6.10 [9.6.9]: https://github.com/sebastianbergmann/phpunit/compare/9.6.8...9.6.9 [9.6.8]: https://github.com/sebastianbergmann/phpunit/compare/9.6.7...9.6.8 [9.6.7]: https://github.com/sebastianbergmann/phpunit/compare/9.6.6...9.6.7 [9.6.6]: https://github.com/sebastianbergmann/phpunit/compare/9.6.5...9.6.6 [9.6.5]: https://github.com/sebastianbergmann/phpunit/compare/9.6.4...9.6.5 [9.6.4]: https://github.com/sebastianbergmann/phpunit/compare/9.6.3...9.6.4 [9.6.3]: https://github.com/sebastianbergmann/phpunit/compare/9.6.2...9.6.3 [9.6.2]: https://github.com/sebastianbergmann/phpunit/compare/9.6.1...9.6.2 [9.6.1]: https://github.com/sebastianbergmann/phpunit/compare/9.6.0...9.6.1 [9.6.0]: https://github.com/sebastianbergmann/phpunit/compare/9.5.28...9.6.0

At NFC Pay, your privacy is of utmost importance to us. This Privacy Policy outlines how we collect, use, share, and protect your personal information when you use our services, including our website and mobile applications.
1. Information We Collect

Personal Information: We may collect personal information such as your name, email address, phone number, date of birth, and payment card details when you register for an account, make payments, or engage with our services.
Transaction Data: Information related to your transactions, including the amount, date, time, and merchant details.
Device Information: Data such as IP addresses, device type, operating system, and unique device identifiers.
Location Information: We may collect your geolocation data when you use our app for location-based services.
Usage Information: Information about how you interact with our services, including access times, pages viewed, and links clicked.

2. How We Use Your Information
We use the information we collect for the following purposes:

To Provide Services: To facilitate payments, manage your account, and deliver customer support.
To Improve Our Services: To enhance the performance and functionality of our app and website, and to develop new features.
To Communicate with You: To send you updates, security alerts, and support messages.
For Security and Fraud Prevention: To monitor, detect, and prevent fraud, unauthorized transactions, and other security issues.
To Comply with Legal Obligations: To fulfill our legal, regulatory, and compliance obligations.

3. Sharing Your Information
We may share your personal information in the following circumstances:

With Service Providers: We may share information with third-party service providers who perform services on our behalf, such as payment processing, data analysis, and customer support.
For Legal Reasons: We may disclose information to comply with applicable laws, regulations, legal processes, or governmental requests.
Business Transfers: In the event of a merger, acquisition, or sale of all or a portion of our assets, your information may be transferred as part of that business deal.

4. Security of Your Information
We take the security of your personal information seriously and implement a variety of security measures, including encryption, secure servers, and access controls, to protect your data from unauthorized access, disclosure, alteration, or destruction. However, no method of transmission over the internet or electronic storage is completely secure, and we cannot guarantee its absolute security.
5. Your Privacy Rights
Depending on your location, you may have certain rights regarding your personal information, such as:

Access and Correction: You may request access to or correction of your personal information.
Deletion: You can request that we delete your personal information, subject to certain exceptions.
Opt-Out: You may opt out of receiving promotional communications from us by following the instructions in those messages.

6. Third-Party Links
Our services may contain links to third-party websites or services. We are not responsible for the privacy practices or the content of these third-party sites. We encourage you to review the privacy policies of those third parties.
7. Children’s Privacy
Our services are not intended for individuals under the age of 13. We do not knowingly collect personal information from children under 13. If we become aware that we have collected personal information from a child under 13, we will take steps to delete that information.
8. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. We will notify you of any significant changes by posting the new Privacy Policy on our website and updating the effective date.
9. Contact Us
If you have any questions or concerns about this Privacy Policy or our data practices, please contact us at:
Email: support@nfcpay.com

Useful Links

Subscribe