The Lane platform is always improving and updated on a weekly basis. New features and functionality are added, known issues are addressed, and the look and feel of the platform evolves for easier and more intuitive use.
Before a new feature is released, it undergoes extensive testing and validation at multiple levels:
- Design Reviews between the Product Designers and Product Developers to understand what the new feature will look like and how it will perform before any work is started.
- Code Checks and Code Reviews within the Product Development team to ensure the new code meets established standards.
- Functional verification by the Quality Assurance team to ensure the new code does what it is supposed to do.
- Regression Validation through a series of automated tests to make sure the new code doesn’t break any existing code.
- User Acceptance review with the Product Design team to ensure the new feature meets the initial design specifications.
- Multiple releases on different instances of the platform, from Development to User Acceptance Testing to Staging and finally Production.
In a complex platform with many moving parts, issues can occur or reoccur. When this happens, the issue is reported and logged, and sent back to development to review further.
Types of issues
- Client-reported: issues reported by a customer are logged as a Help Desk ticket and also reported internally with the development team.
- Regression: issues where a new feature or fix affects existing functionality or causes a previously fixed issue to recur.
- Automation: issues found through automated testing performed on each build.
- Feature Request: When an issue is reported but the platform is functioning as designed, a Feature Request is logged to improve the experience or evaluated for future development by the Designers.
What happens when an issue is reported
When an issue is found and reported, the Support team will attempt to re-create it on another channel or instance. This helps narrow down the cause of the problem.
- If the cause of the problem is due to a misconfiguration or a misunderstanding of the feature, the Support team will describe the solution with links to supporting Help Center documentation if available.
- If the cause of the problem is determined to be due to a bug, an internal ticket is created and assigned to the development team responsible for that area.
The development team works on a prioritized list of issues each week, called a sprint. Once a weekly sprint is complete, the new code is sent through a multi-step process for validation before it appears live on our clients’ apps.
Once a developer has created a fix, a member of the QA team checks it against a list of Acceptance Criteria. It may be accepted or sent back to the developer if issues are found.
Release Regression Testing
For every release, there is a list of test scenarios involving integrations and basic functionalities that are always executed including: mobile access integrations, notifications, SAML integrations, purchases and more.
Regression test cases are automated as much as possible to efficiently cover the most common admin workflows including the content editor, content targeting, publishing, and basic admin functionality. Tests are run at least twice daily on all developing code, against a variety of scenarios and test cases.
Each internal environment (Development, UAT, and Staging) has a corresponding mobile app for testing on iOS and Android. This allows for testing on mobile at each stage of the process, and for testing mobile-only features.
Normally all testing is done on the Lane White Label (Lane’s core application) versus our clients’ branded applications, since the only main difference from other White Labels is branding.
When new integrations, such as connections to Angus, HID, and other solutions, they follow the same process as with new features. Product Design and Product Development work together to ensure the new integration meets the design specifications and fits with existing features and functionality.
As the development teams work on releasing new features and approve bug fixes, a list is compiled which are then used to create Release Notes. Documentation is created on how to use the new function or feature, and a list of fixed issues is made available as an article in the Help Center.
Product Development is a complex process with many moving parts. If you have any issues to report, contact the Help Desk as firstname.lastname@example.org and we will be happy to help you investigate, report, and track the issue towards a successful resolution.