Two men sit next to each other and work on laptops

Spryker MVP with clear baselining and test automation

Günter GlasauerApril 2021

Spryker Features in MVP

For your MVP, you select exactly the functions from the Spryker product structure that you currently need. For example, Product Management, Checkout, and Payment. No more and no less. A function, called a feature in the Spryker context, consists of various modules that have dedicated version statuses.

To further develop your product based on the MVP, rely on professional project management from the start. Clear baselining, i.e., the specific version of a configuration, and a high degree of test automation ensure the necessary agility. This way, you maintain an overview of your product extensions. Changes are also continuously possible without additional processes: Which version of which module belongs to which version of my product. You should always keep this point in mind.

Our Technology Partner

B2B, B2C and Market Places – Digital Commerce With Spryker

Spryker

Clear Baseline for Each Release

Implement clear baselining in both requirements management and implementation. No scope creep! This way, you develop and test only the features to be released within scope.

Test-Driven Development and Automated Integration Tests

Keep the high quality of your product in mind and regularly check if functions from earlier releases continue to work.

Actively encourage developers to implement "Test-Driven Development" (TDD) as a design strategy. Continuous development and refactoring throughout the development process promise quality software. Based on the acceptance criteria, define the scope of integration tests. Rely on a high degree of automation. This way, you maintain the flexibility to use Spryker modules according to requirements. The commerce system supports the compatibility of your releases through the application of the Facade Pattern.

Spryker's Glue REST API is the target of automated tests, against which the implementation then takes place. Developers first write the integration tests and consequently implement the functionality. Largely automated frontend tests by QA complete your test set. Creating test scripts increases the initial implementation time for a feature. Over time, however, you significantly reduce the regression testing effort. And that is essential for an optimal time-to-market goal.