- What is lendo-stp-gdansk/lendo-fixtures-bundle and what does it do?
- It is an internal Composer package from Lendo STP Gdansk that provides a fixtures engine plus commands for Lendo projects. Its stated purpose is to supply reusable test data, seeders, and factory helpers so teams can build integration tests and demo environments without hand-crafting sample records. The overview does not document the public API, so the exact capabilities must be confirmed from the source and composer.json before adoption.
- Is lendo-fixtures-bundle a Laravel package or a Symfony bundle?
- The name uses Symfony's bundle vocabulary, but that alone does not prove it is a Symfony kernel bundle. It could be a Laravel package named by convention, a Symfony bundle that happens to install in Laravel, or framework-agnostic PHP wrapped in a bundle shell. Check the composer.json type and require constraints plus the service provider or bundle class to determine which model it actually follows.
- How do I install lendo-fixtures-bundle in a Laravel application?
- Install it with Composer using the vendor and package name, but expect to need access to a private repository or VCS path repository first. Because it has no validated public registry footprint, a plain composer require may fail without credentials configured in Composer and CI. After installation, confirm whether it registers a Laravel service provider or requires manual registration before running any fixture commands.
- Which Laravel and PHP versions does lendo-fixtures-bundle support?
- The supported version matrix is not stated in the package overview and cannot be inferred from a zero-footprint public registry listing. Review the require and require-dev blocks in composer.json for PHP, Laravel, Symfony, and extension constraints. Also check whether the package is actively updated for new PHP and Laravel majors, since an internal package without external dependents may lag behind.
- Does lendo-fixtures-bundle work with Eloquent or is it coupled to Doctrine?
- This is the key technical unknown: many fixture engines are built around Doctrine Data Fixtures or Alice-style loaders, which would not integrate cleanly with Eloquent and Laravel migrations. The overview does not specify the data layer, so inspect the engine's public API and dependencies for Doctrine, Eloquent, raw PDO, or a driver abstraction. If it targets Doctrine only, an adapter may cost more than writing native Laravel seeders and factories.
- How is the package distributed, and do I need private repository credentials?
- Given the internal vendor namespace and the absence of stars, dependents, or a validated public registry footprint, it is most likely consumed through a private Composer repository, Satis or Toran proxy, or a VCS path repository. That means installation is gated on access credentials and CI secrets rather than on technical merit alone. Confirm the authentication story and supply-chain review process with the maintainers before planning integration work.
- How does lendo-fixtures-bundle compare to Laravel model factories, seeders, and Faker?
- Laravel already ships model factories, DatabaseSeeder, RefreshDatabase, and Faker, which cover most fixture needs out of the box. The bundle's plausible value is a declarative scenario DSL, dependency graph resolution, and cross-project fixture sharing that improves parity between Lendo services. Adoption should be justified by a clear capability delta over native factories, not by convenience alone.
- Are the fixtures deterministic and reproducible, and how does it handle truncation or idempotency?
- The overview does not document a determinism or seeding guarantee, so reproducible fixtures are not confirmed. Ask the maintainers whether the engine accepts a fixed seed, how it orders and resolves fixture dependencies, and whether repeated runs truncate, upsert, or fail on duplicate records. Without a documented idempotency and truncation model, parallel test runs and shared demo databases carry real risk.
- Is it safe to run lendo-fixtures-bundle in production or shared environments?
- Treat fixture and seed tooling as high blast radius because it writes records directly to databases. A misconfiguration could seed a shared or production-adjacent environment with synthetic but realistic records, potentially including PII-shaped data. Gate the commands behind environment checks, restrict credentials, and confirm whether the bundle includes any built-in production safeguards before enabling it anywhere beyond local and CI databases.
- Who maintains lendo-fixtures-bundle, and what are the alternatives if access or support is a problem?
- It is an internal single-organization package with no public issue traffic, which implies a small maintainer group and limited external validation. Confirm the owning team, support channel, and any documented response expectations before depending on it in critical test suites. If access, maintenance, or ORM compatibility proves problematic, native Laravel factories and seeders combined with Faker remain the most reliable alternative.