Simulating real-user scenarios as part of your automation is a solved problem. You need to understand the domain, the product, the user, and then define and implement your scenario.

But there are some types of scenarios that are complex to implement. These are the real-world scenarios having multiple personas (users) interacting with each other to use some business functionalities. These personas may be on the same platform or different (web / mobile-web / native apps / desktop applications).

Example scenarios:

• How do you check if more than 1 person is able to join a zoom / teams meeting? And that they can interact with each other?
• How do you check if the end-2-end scenario that involves multiple users, across multiple apps works as expected?
  • Given user places order on Amazon (app / browser)
  • When delivery agent delivers the order (using Delivery app)
  • Then user can see the order status as "Delivered"

Even though we will automate and test each application in such interactions independently, or test each persona scenarios independently, we need a way to build confidence that these multiple personas and applications can work together. These scenarios are critical to automate!

In this session, I will demonstrate teswiz, an open-source framework that can easily automate these multi-user, multi-app, multi-device scenarios. I will also mention how to run these tests on local and in CI pipelines.

Example: Multi-user, Multi-device test scenario

Example: Multi-user, Multi-app, Multi-device test scenario

Teswiz enables, and guides you to implement your automated tests while adhering to the principles of test automation, like - independent tests that run in parallel, against multiple environments using environment-specific-test-data and generate rich and contextual reports (and test execution trends) in reportportal. 

Test coverage is increased by using Applitools Visual AI, along with Applitools Ultrafast Test Cloud. 

In addition, teswiz takes away the pain of managing your browsers, and android / ios / windows devices for automation. The automated tests can run on local browsers / devices, or against any cloud provider, such as HeadSpin, BrowserStack, SauceLabs, pCloudy.

The following features makes teswiz unique:

The ability to do:

• Multi-user scenario automation between all platforms (android, iOS, Web, Windows desktop applications)
• Managing browsers / devices and parallel execution automatically
• Completely configurable options - means no code change required to run different combinations of tests, on demand
• Integration with Applitools Visual AI and Applitools Ultrafast Test Cloud
• Rich contextual reports (including screenshots, browser / device logs) and trend analysis via ReportPortal.io

The following features are relatively new in teswiz:

• Ability to run test orchestration across different platforms, using different app(s) and different users
• Integration of Applitools Ultrafast Grid for scaling
• Support for Firefox & Safari (earlier it was only Chrome)
• Better driver management & cleanup

Building on the work undertaken over the last two years producing a Code of Ethical Conduct for Agile Coaching, this workshop invites participants to explore the latest version of the Code and then examine a variety of ethical scenarios to see how the code plays out in real life situations.
Participants are invited to add their own examples to the scenarios which can serve as learnings for future readers of the code and associated scenarios.

Often the word DevOps connotes cloud infrastructure and a set of tools and hence existence of the DevOps teams in many organizations.  This categorisation and organization is the projection of understanding existing tools and practices to an emerging category and an attempt to co opt or assimilate new tools and ideas. This categorisation fails to take into account the basis of DevOps movement.

In this talk, I will be covering the motivations and incentives for DevOps movement and why it is successful when it is applied with a first principles approach.

If you look at any activity, there are subtle motivations and tradeoffs which direct our actions. The idea of transaction cost for a given transaction is such a subtle backdrop for many of our seeming irrational actions. From farmers going to a loan shark instead of banks to the rise of nfts and tokenization. Ronald Coase back in 1937 asked a fundamental question: If the markets are so efficient, why do companies exist? The essay is an excellent read on how organic organizations emerge nudged by intrinsic forces like transaction cost. What Coase found out was the trust between two individuals is the most costliest of the resources.

The lack of trust increases the transaction costs of business transactions and a structure where trust can be established more easily, brings down the transaction cost and hence subsequently the cost of goods and services.

So how does this apply to DevOps thinking? In my talk I will show how we can leverage this thinking to reduce batch sizes and thus increase flow and effectiveness of the teams.

From a waterfall caterpillar to an agile butterfly that’s my journey and also what I am doing at my organization.

Agile transformation in KPOs(Knowledge Processing Operation) is a big challenge due to the nature of the work.

Join my session to find ways to do agile transformation of this industry based on my decade of agile coaching experience and recently transformation of a 600 strong team. I would like to share the opportunities and challenges faced while transforming the knowledge industry of an B2B whole seller.

The talent war remains heated, especially for Digital and analytics talent.  But a skills inventory, expanded talent pipeline and cool sourcing can only get managers so far when it comes to hiring.  Hiring & retention programs need design thinking treatment — a human-centric problem-solving approach that explores a wide range of possible solutions, extensive prototyping and testing.   How organizations reimagine hiring and talent management processes in an persona based  talent-centric way that’s delightful is going to be the unlock.  How do we make our processes and experiences engaging?  We live in an experience-based world – and individual customer-centric experience has been the true driver behind massive improvements in key journeys like how we pay taxes, how we order our morning coffee, how we shop online.  However, hiring people – or looking for a job- often still feels like a root canal – complicated and painful. How organizations hire and manage our technology talents will be a key differentiator.

Drawing on the research and content published on InfoQ.com over the last 12+ months, this talk summarises the state of play in engineering culture in 2022.
Key points that will be explored in the talk are:

• Hybrid work needs careful redesign and reassessment of the workplace and will be a
  significant challenge going forward
• Culture matters more than ever before as people are reassessing their options around
  workplaces and styles
• Culture can and should be made visible and tangible
• IT teams are tired, and burnout is a serious problem the industry needs to tackle
• Team topologies and being deliberate about team formation are aspects of culture design
  that can support better outcomes
• The gaps between good and bad workplaces are widening and people are voting with their
  feet (or video conferencing cameras)
• Leadership styles and approaches need to evolve to support the needs of teams and
  individuals today
• Paying attention to physical and mental wellness matters and can’t be treated as an
  afterthought