- How do I install mrgoodbytes8667/test-twitch-faker in a Laravel project?
- Install it as a development dependency with Composer, for example composer require --dev mrgoodbytes8667/test-twitch-faker, after confirming its PHP and Laravel constraints in composer.json. Because v0.0.7 is pre-1.0, pin the exact version and review the v0.0.6 to v0.0.7 diff before adopting. Keep it out of production dependencies.
- Does mrgoodbytes8667/test-twitch-faker hit the live Twitch API or need credentials?
- The package is designed to fake Twitch API responses so tests avoid live network calls and Twitch credentials. The TPM notes say you should still confirm that it does not perform hidden network calls when you adopt it. A CI spike and offline test run can verify that behavior.
- Which PHP and Laravel versions does test-twitch-faker support?
- The provided release information does not list explicit PHP, Laravel, PHPUnit, or Pest version constraints. You must inspect the package composer.json and release diff before relying on it. Do not assume Laravel auto-discovery or facade support without checking package metadata.
- How do I stub Twitch endpoints with test-twitch-faker in Pest or PHPUnit?
- The package provides fluent response stubbing for Twitch endpoints and is intended to replace the real Twitch client via Laravel's service container. The exact stubbing syntax is not included in the provided context, so check the README or source for method names. Then use the fake in your PHPUnit or Pest test setup before exercising your application code.
- Can I assert outgoing Twitch API requests in Laravel tests with this package?
- Yes, request assertions are listed as a feature so you can verify outgoing Twitch interactions in tests. Use them to confirm the endpoints and payloads your application sends without contacting Twitch. Review the package docs for the supported assertion methods.
- Is test-twitch-faker meant for production or only for tests?
- It is a test-only helper and should be installed as a require-dev dependency. The TPM recommendation is to keep it out of production service providers and runtime paths. Use it to make Twitch integration tests deterministic and offline.
- What changed from v0.0.6 to v0.0.7 of test-twitch-faker?
- The available release notes for v0.0.7 only include a changelog compare link and do not disclose explicit features, fixes, breaking changes, or deprecations. Review the actual diff before upgrading a pinned version. Do not upgrade solely because a new 0.0.x release exists.
- Does test-twitch-faker use Laravel HTTP client fakes or its own interception?
- That detail is not confirmed in the provided context. The TPM assessment explicitly recommends checking whether it uses Laravel's HTTP client fakes or a separate interception mechanism. This matters for compatibility with your existing HTTP fake patterns and test setup.
- What are the risks of adopting a pre-1.0 Twitch faker package?
- In 0.0.x versions, even patch releases can include breaking changes, so version pinning and upgrade review are mandatory. Other risks include single-maintainer or low-adoption exposure, stale Twitch fixtures, incomplete endpoint coverage, hidden network calls, and Composer dependency conflicts. Start with a branch and CI spike before standardizing on it.
- What alternatives exist to test-twitch-faker for mocking Twitch APIs in Laravel?
- You can use Laravel's built-in HTTP client fake, custom test doubles, or other PHP mocking tools to fake Twitch endpoints. The package's value is its Twitch-specific fluent stubbing and request assertions, so compare that against the endpoints you actually use. If coverage or maintenance is uncertain, keep local fakes until the package proves stable.