Can a bot bring Agility?Pooja Shah
schedule 4 months agoSold Out!
A typical conversation on a release day:
Everyone on team running around with questions like how was it merged without review? why wasn't it caught earlier in the automated tests? is it not test covered? And the blame game starts which turns pleasant office premises into a really chaotic one as all starts behaving like Shakuni the bad critic ..............
Does this conversation sounds familiar to you?
yes, in fast paced organisations like us it is a burning problem. And we really wanted a monitoring system in the test phase itself that too using the same tools we use regularly and hence not costing us anything extra. This brings Agility within the teams by having everything & everyone on a single platform and help everyone feel what’s there in the black box.
Points needed to ensure:
- Prevent direct push to the branches we want to protect
- No commits to go inside without tech/product review
- A common transparent place to quickly go through all commit links/description with timestamp to quickly know which can be the culprit commits
- Alerts to respective team members for any suspicious activity done by anyone
- Personalised alerts to the committer for reminding to follow the release process
- As the team size grows, assisting each one in the team on release process & progress is really a repetitive task and an unnecessary dependency
In this talk, we will discuss about unleashing the power of Github & Slack to create a interesting code monitoring and talking bot which keeps everyone in a team updated on a single platform.
From Pyramids to hourglass - New approach for digital apps testingSreevatsa S
schedule 4 months agoSold Out!
About the session: One of the first things you learn when you enter the quality assurance space is the famous triangle breakdown with Unit test at the bottom, Acceptance Tests based on API on top of that (in some places this layer is integration tests but the idea is the same) User Interface (UI) Tests at the very top. This Pyramid has been the main principle on how to approach testing activities (mainly automation) for the past two decades. Flash forward to the present, and we have all been taking part in the "Digital Transformation" happening all over the industry. Mobile Native applications, as well as web applications, take part in almost every activity we do throughout the day, so businesses are building their strategy and shifting resources to deliver applications, while maintaining cost and market share. So what changed? Users are no longer static, they are interacting with apps while on the train heading to the office, while waiting for a flight at the airport, or drinking coffee before their next meeting – these “interactions” are done mostly the user is on-the-go with mobile device. Additionally, applications can now take advantage of sensors within the device to provide a better user experience. The environment where our end users use our application has significant impact on the functionality and performance of our application. At the end of the day, we call this "quality". In the last year we developed a new approach for digital application testing – The “Hourglass” – This new approach expands the well-known "Pyramid" and updates it to the digital era. The client side is now richer and contains many components that impact quality of application. It redefined the definition of coverage. At the top of the pyramid we added 2 additional triangles (to give the hourglass shape). The first triangle is devices – what devices should we test? How we should approach the changes that happens in the device market? The second triangle is environment - where will our end user interact with the application? We've leveraged our investment in automation to get real digital coverage, which helps you reach high quality applications.
Testing systems that responds to changing business conditions
How do you test a system which promises to do something but never says when? How often have we heard people saying in Distributed systems, " Not our fault! Our system encountered error due to changes made in other system." If you have faced situations like these on your project, join in to know how we dealt with them.