In this blog post you’ll read about our successes and challenges as we tried our hand at Ensemble (Mob) Testing
At Pendo, we’re always trying to push the boundaries of testing. We believe that incorporating new approaches is key to promoting our quality culture and a quality focused mindset within our teams. We actively promote that everyone is responsible for quality and constantly strive for more collaboration and knowledge sharing to assist everyone on our quality journey. We have always found value in exploratory testing and recently tried two different approaches to enhance and improve our approach to this key testing activity.
WebAssembly (Wasm, in short) is an assembly-like instruction format for a stack-based virtual machine. It is designed to be encoded in an efficient binary format that can be executed at near-native speed on any platform that can host the virtual machine. In particular, this is supported on all modern browsers (Chrome, Edge, Firefox and Safari).
Pendo’s Jonathan Thompson showcases the power behind the intercept() method in Cypress – by providing examples of request interceptions, mocks, and assertions. Read: Improve Your End to End Tests with Cypress Intercept
Books fetch request highlighted in red. (Screenshot by Jonathan Thompson)
At Pendo we are always looking to enable our customers to gain insights into their products so they can invest in building the right features for their users. One of the key methods for doing this is to dig into the data. We have a lot of cool tools such as Dashboards, Data Explorer, and Retention to display that data in a meaningful way.
At Pendo, we collect tons of data, and we’re always finding new ways to showcase that data so our customers can see how their apps are being used and can make their software more lovable. One of the data visualizations we have been working on recently is Product Engagement Score. To calculate a Product Engagement Score, we combine Stickiness, Growth, and Adoption to show how invested users are in that product.