Valeriy Nayda - Best Practices in Magento 2. Based on Multi Source Inventory (msi) project

Magento PWA Studio not just for Magento: it’s for making all kinds of Progressive Web Apps. And it’s not just for PWAs: it’s for helping developers to get work done. Though we conceived PWA Studio as the way to create PWAs that belong in the extensible Magento ecosystem, we are building it to be useful for any frontend developer, inside or outside the world of Magento. Our standard app architecture uses beloved modern frontend ingredients. You may already know them; if not, you can learn them from a large online community. As Magento joins the busy world of modern Web frontend, you can join us there too. Come see the many ways you can use PWA Studio tools and the many ways you can contribute to them.

This document discusses Oleksandr Lyzun's experience working on several Magento Community projects including Async/Bulk API, GraphQL, PWA, and Asynchronous Import. It provides details on the goals and status of each project, how they improve the Magento experience, and benefits of contributing to open source Magento projects. The document also references resources like the Magento Community Portal and Backlog for finding additional projects to contribute to.

This document discusses Magento's approach to backward compatibility (BC). It explains that Magento uses semantic versioning to minimize breaking changes. Magento aims to balance keeping the codebase BC while still fixing flaws. The document outlines what constitutes public APIs and SPIs and how modules should depend on these. It provides examples of permitted and prohibited code changes to maintain BC. It acknowledges that BC fixes can look ugly but emphasizes the importance of continuous refactoring to improve code quality over time.

The document discusses Magento 2.3's new declarative schema feature for managing database schemas. Declarative schema provides an alternative to setup scripts that avoids issues like missed SQL operations and makes rollbacks and testing easier. It works by declaring schema elements like tables, columns, indexes in an XML file. Modules can then be installed and uninstalled while maintaining the expected schema state. The document covers how to declare different database elements and use features like dry-run testing and safe mode operations. It also discusses converting existing modules from setup scripts to the new declarative schema.

This document summarizes Magento's Extension Quality Program (EQP) process and findings. It reports that 50% of submitted extensions fail to compile in production mode, and of those that do compile, only 25% pass manual quality assurance testing. The top 5 issues found are extensions not compiling in production mode, compiling but not working properly in production mode, incompatibility with claimed Magento versions, poor error handling, and lack of adherence to coding standards. The document outlines planned improvements to the EQP including increased automation of testing and integration with Magento Marketplace.

Power Tomorrow: Understanding Magento 2.2 Credit: Magento Live India 2017 Website: http://magentolive.com/in/

For ISVs who are currently providing solutions to individual subscribers or system integration (SI) partners via unmanaged packages, org-dependent unlocked packages can provide a better & faster implementation experience as well as improve stability.

This presentation was delivered as part of the Rapise webinar series and highlights the latest features in Inflectra's scriptless test automation platform - Rapise v6.6. The presentation covers: - Rapise 6.6 new features: CI/CD integration, Git integration, and Framework building. - Rapise 6.6 system enhancements: Reporting, Rapise Launcher, API Testing; new Actions to already supported Objects. To learn more about Rapise, visit https://www.inflectra.com/Rapise/

The slides from the third Manchester Meetup, this time online. A slide deck explaining the use of RAML and how extensions allow you to separate the code required for service contract or interface and that of the implementation.

Arno Brugman - How to Engage: Customer/Partner Engagement Angel Alberici - DIY API Led with Alexa "The Contest App"

Name: Bob Nemec Title: Seaside based custom ERP system youtube: https://youtu.be/ehZtXx-rjx4 Type: Talk Abstract: TRAX is a custom, in-house Seaside ERP system written for, and used by, HTS, an industrial HVAC sales company. We use VisualWorks to build, manage and test the code, and GemStone to deploy it. Running since September 2015, the application continues to be developed and adapted to the changing needs of the business. This talk will highlight some of the design choices and technical decisions we’ve made, and the agile development process we use. Bio: Bob Nemec is the Software Architect of TRAX. Bob has worked with Smalltalk since 1990, and used it exclusively to build commercial systems since 1994.

Speaker: "Using the Mule 4 SDK to build a connector" session with Chris Hughes, Strategic Advisor at MuleSoft Host: Angel Alberici Youtube: Virtual Muleys (https://www.youtube.com/c/VirtualMuleysOnline/videos) Meetups: https://meetups.mulesoft.com/online-group-english/ https://meetups.mulesoft.com/events/details/mulesoft-online-group-english-presents-using-the-mule-4-java-sdk-to-build-a-connector/

Slide 1 - Arno Brugman - How to Engage Partners/Customers Slide 42 - Angel Alberici - API Led with Alexa Host: Angel Alberici Youtube: Virtual Muleys : https://www.youtube.com/c/VirtualMuleysOnline/videos How to Engage: Customer/Partner Engagements This session is for Developers, Engineers, Architects, C4E & Integration Stakeholders, Partners, SIs and Contractors who want to learn about the prerequisites and requirements for a successful Customer/Partner Engagement. In this session we will answer the following questions: Can you provide basic guidelines to avoid the most common pitfalls? Will our Partner act as a Thought Leader? How do we ensure our Partner designs and implements with reuse in mind? How do we verify the work delivered by our Partner? What information should you share with your Partner? What should you request (ask) from your Partner? How should you Engage with your Partner? Although the slides are presented from the Customer perspective, the session will be of value to Partners, SIs and Contractors too. After this session, you will know what information needs to be shared between Customer and Partner and how Customer and Partner should engage to ensure successful adoption of the Anypoint Platform and consistent generation of Business Outcomes (value). DIY: API Led with Alexa “The Contest App” You saw it and now you want to Do It Yourself (DIY). Session aimed towards Devs/Engineers and enthusiasts/hands-on Architects/Consultants who want to create their own API Led with Alexa application. Agenda: Speedrun on APLC/SDLC Successful stories Participate in the Contest and win prizes! How does it work? How to do it yourself? Where is the value in using API Led for this case?

Inflectra is proud to bring you a highly anticipated Spira v.6.3 and a webinar to go with it. Presented by Technical Director Adam Sandman, this webinar goes over the major enhancements available in SpiraTest, SpiraTeam and SpiraPlan version 6.3.

These are the annotated slides of the presentation I gave at MageConf 2017 on Dec. 16 in Kiev, Ukraine

Functional Programming for Service Layer architecture. Examples of API evolution on Magento 2 codebase

The best practices around your upgrade from Magento 1 to Magento 2. See example and other factors that will impact your upgrade.

Testing in Magento 2 by examples of Multi-Source Inventory Project (MSI) - Unit Testing and how to do them right. - Tautological Test Driven Development - Integration Testing - Example of Reservation mechanism in MSI and Integration test coverage for it - Web API testing (REST, SOAP)

This document discusses how Magento software is open source and how developers can contribute to its development. It provides background on open source software and outlines Magento's process of becoming more open source over time through transparent commits, public pull requests, and addressing issues. The document encourages developers to validate issues, fix issues by creating pull requests, contribute to patch releases, and conduct innovations. It describes the Magento Multi Source Inventory project and opportunities for developers to get involved through the community Slack channel or contribution days.

Presentation for Meet-Magento Indonesia 2021. It describes what the Hyvä Theme for Magento is and how it is working with it from a (mainly backend) developer perspective.

Magento automated tests overview: - Advantages/disadvantages of unit testing. - Integration tests in Magento. - Testing Magento WEB API. - Frameworks for functional testing. Tests as XML configuration. - Best practices.

The document discusses Magento's transition from the Magento Testing Framework (MTF) to the new Magento Functional Testing Framework (MFTF). MTF had challenges like reliability, maintainability, and ease of use. MFTF was created to address these and enable lower costs, faster test creation, and support new strategies like bundled extensions. MFTF uses PHP, Composer, XML, Codeception and other tools. It focuses on maintainability, readability, performance and customizability through features like reusable page sections and mergeable test files. The document provides examples of MFTF's code structure and explains how tests are selected and executed through the Robo task runner.

The document provides Magento's technical guidelines for developing code. It outlines best practices for strict typing, class design using composition over inheritance, dependency injection, exception handling, and separating application layers. The guidelines are intended to promote extensibility, customizability, and maintenance of Magento code. Key aspects include using interfaces to define dependencies rather than direct object references, single responsibility per class, and limiting coupling between classes.

Let's do a deep dive into two Innovations Lab winner projects, check the details, and how to apply your first project. You will be able to check how to get ideas and how my innovation projects works, looking directly into the code.