Discover TestMetry

The world of IT is evolving every day, and it is essential to learn about the latest industry trends and be relevant in your workplace. I am here to share my experience and learnings around RPA, Test Automation, UX, and DevOps that I have gained in the last two decades by working in both the product development and the IT services world!

ta_edited.jpg


There is a high demand for speed to market while maintaining quality in today's business world. Many businesses face a variety of challenges when it comes to faster release and deployment to production. Several organizations encourage their teams to receive continuous feedback from the manufacturing environment.


One "shift-right" testing method is becoming more popular, even though many believe testing in production is risky. From my experience, I have seen this approach working in various domains like Retail, Health Insurance, etc. For example, while I was working for a global retailer, we had our testers visiting stores before they were open to test the new Point of Sale release by executing transactions on the Point of Sale Terminals. By doing this, we got real-time feedback about any potential issues with the build before it went live in all stores. Not only did this help ensure a higher quality release, but it also saved time and resources by catching potential issues early on.


I've also witnessed testing teams run automated tests in production to perform smoke tests. Another use case was executing the test cases that were not covered as part of your SIT and UAT due to test environment constraints. Still, one must-do practice: ensuring that manual or automatic checks do not modify existing data or create new records. This means they should only cover read-only activities like searching for customers, opening screens, etc. Also, as you might get limited time to carry out the tests in a production environment, one should be looking at automating the testing to the maximum extent possible.


Several "shift right" testing techniques have emerged in recent years that aim to shift the responsibility for testing from developers to users. Synthetic user monitoring, real user monitoring, code instrumentation, dark launching, feature flags, canary release, blue-green release, and A/B testing are all examples of shift-right testing techniques that can be used to improve the quality of software products. We will be covering each of these techniques in detail in subsequent posts.


There are several benefits to shift-right testing, including:


1. Real-time feedback: As mentioned above, one of the most significant benefits of shift-right testing is that it allows you to get real-time feedback from your target audience. This is especially beneficial for time-sensitive or mission-critical releases, as it can help ensure a smooth deployment with fewer issues.


2. Increased collaboration: Another benefit of shift-right testing is that it increases collaboration between various teams, such as development, QA, and operations. By involving all stakeholders in the testing process early on, you can ensure that everyone is on the same page and that there is a clear understanding of the release goals.


3. Faster deployments: Shift-right testing can also help speed up your deployments by catching potential issues early on. This saves time and resources, helps reduce risk, and increases confidence in the final release.


4. Improved quality: Last but not least, shift-right testing can help improve the overall quality of your releases by detecting potential issues early on. This saves time and resources, helps reduce risk, and increases confidence in the final release.


In conclusion, shift-right testing is a beneficial way to test in production and should be considered as part of your strategy. This testing helps catch defects early on and prevents them from going into production. If your business is looking for a way to improve its release and deployment process, shift-right testing is worth considering.


Engineers, what are your thoughts on testing in production? Have you been able to do it before? What were your results? Please share your experience below!

0 views0 comments



Chaos engineering is the practice of intentionally injecting faults into a system to test its resilience. Doing so can identify potential issues and mitigate them before they cause any significant problems. Azure Chaos Studio is a fully managed chaos engineering experimentation platform that will help you discover those hard-to-find problems. So whether you're in late-stage development or production, Azure Chaos Studio has covered you.


With Azure Chaos Studio, you can put your Azure applications through actual or simulated faults and observe the response and behavior of your applications to real-world disruptions. Plus, there's a vast collection of templates with reusable chaos experiments to help you get started.

Azure Chaos Studio is an excellent tool for software engineers who want to add chaos engineering to their workflow. With Azure Chaos Studio, you can easily integrate chaos tests into various phases of application development. In addition, the platform has a vast collection of templates with reusable chaos experiments. So whether you're just starting with chaos engineering or a seasoned pro, Azure Chaos Studio has something to offer everyone.

If you're looking for a way to add some chaos to your life, look no further than Azure Chaos Studio. You can find additional details here if you'd like.
👇👇👇

https://lnkd.in/g83QDVS6



A good test engineer is both methodical and creative. They understand how to put themselves in the customer's shoes and think about all the different ways a product could be used. They also have a keen eye for small details and know how to use various tools and technologies to their advantage. Here are seven skills that every good test engineer should possess. 👇👇👇

1. The ability to review requirements: A good test engineer knows how to review and analyze requirements. They also know how to identify gaps and inconsistencies. This skill is crucial because it ensures that the tested product meets all the requirements. Also, a test engineer identifying issues upfront will help identify defects earlier, reducing the cost of defect fixes. 🔍🔍🔍

2. The ability to think like a customer: Testers should know how to put themselves in the customer's shoes while designing and executing tests. They understand that customers can be unpredictable and think about all the different ways a product could be used. Generally, most test design techniques do not help identify out-of-box scenarios; this skill is essential to ensure that the tested product is user-friendly and meets the customer's needs. 💡💡💡

3. A strong understanding of the domain: A good test engineer understands the domain they are testing. This skill is vital because it helps ensure that all scenarios are considered and that no details are overlooked. For example, if you are testing a healthcare application, you need to know regulations like HIPAA, standards like HL7, patient workflows, etc. 🗂️🗂️🗂️

4. The ability to manage time: A tester should know how to manage their time effectively. This skill helps ensure that deadlines are met and that products are released on time. For example, a tester working in an Agile Sprint will get 15 or 20 days to design and execute tests. Therefore, it is important to identify all the test tasks upfront, estimate the effort, prioritize tasks, and track the effort spent. 🕛🕛🕛


5. The ability to manage emotions: A good test engineer knows how to manage their emotions effectively. This skill is vital because it helps them remain calm under pressure and not get overwhelmed by their work. For example, one may need to handle scenarios like developers not agreeing to defects raised, a project manager asking you why a defect was not identified, requesting you to skip some tests, etc. 😊😆😔😨

6. Strong written and verbal communication skills: A test engineer should focus on acquiring written and verbal communication skills. Written communication skills will help to prepare test cases and document results and defect reports effectively. Effective verbal communication skills will help to communicate with developers, managers, and business analysts in status meetings, defect triage meetings, walkthroughs, etc. ✍️✍️✍️


7. The ability to keep up with technology and tools: Testers must keep up with the new technology and tools to their advantage. Knowledge of the underlying technology and platform will help identify test types, understand the technology limitations of your application, etc. Also, acquiring skills in various tools will help the tester to be more productive. For example, developing skills around a test design tool will allow testers to design high-quality test cases faster. 🧰🧰🧰

We only discussed a few of the skills that are required to be a successful test engineer. A good number of these skills may come naturally; others must be learned through experience or formal training. However, having these skills will help you succeed in this rewarding career!




6 views0 comments

Get in Touch!

Thanks for your interest in TestMetry. For more information, feel free to get in touch and I will get back to you soon!

Thanks for submitting!

Image by Windows