As this new year dawned, I was reminiscing on the fact that I now had more than a decade worth of experience in the IT industry. Back when I started my career, I had a very strong notion of what a successful career would look like at the 10-year mark. As I look back, I can only shake my head at the simplicity and naivety of that idea. So, here are the things that I would tell the 21-year-old me as she started her career.
The excellent bug report raises the issue and provides sufficient data for a good decision.The article describes why do programmers do not fix some bugs so how to report bugs accurately so that the reader understands the impact of the problem and takes up for fix.It describes RIMGEN a guide for how to investigate bugs and communicate better.It also describes about some good Bug reporting skills for a Tester to improve his credibility.
My thoughts on the concept of shift left in software testing. 1. Shift left simplistically applied to automating everything in sight is not an ideal solution. 2. Morphing all the diverse roles in software engineering to just have all programmers on team leads losing knowledge present with people who understand different facets of creating software. 3. Leaving testing to the end of a project is not a solution either.
It includes my observation regards to position in my career. You have to work on skills instead of chasing only a position without any effort. Sometimes people get a position but are unable to manage it due to skills and never try to overcome it and problems begin from here.
This article is about my unconventional path into software testing at the age of 50. I often see people asking if they are to old to learn to code to old to change careers. It is also about alternative career paths if you just graduated a coding Bootcamp giving people options that they may have never pursued.
Why is test design called test case design? Are writing detailed test cases a design? But how are we identifying the behavior of the software and conditions for the software to get checked? In this article I am trying to share my thoughts on what is test design and what are the skills required to perform test design.
A life transformation of how three different roles and three pieces of advice helps mould a belief to chase after the passion.
The article is all about a Tester’s Expected Learning and Unexpected Challenges Voyage. Today I have been promoted to a Senior QA Engineer role in the firm I work. This made me recollect on my last 8 years of Testing journey and how I ended up in this role. So here I’m to share my lessons learned and at the same time showcase the challenges I faced in my career path.
Organizations are now very much concerned about reliability. To improve reliability organizations must ensure resiliency in addition with other factors like functionality performance stability usability accessibility. Reliability is now one of the top priorities for the organization as it ensures superior end-user experience which in turn creates trust and confidence. As a result organizations can create their own brand identity and survive for longer period. Organizations are now conducting continuous chaos testing to ensure resilience and understand how the system handles failure for better reliability. Overall continuous chaos testing not only ensure resiliency but also assists to learn from the failures. Learning from failures also assist in reliability. In this blog I will talk about how continuous resiliency testing assists application/product owners in steady learning from the failures.
With digital transformations at scale there is a sheer increase in the adoption of cloud-native applications microservices and distributed hybrid deployments. The technical complexity to build & deliver a resilient and reliable IT system has increased multi-fold in the recent years. Although the new-age distributed architectures provide increased scalability and flexibility to release application features rapidly the ability to perform root cause analysis to isolate the faults and fix the issues have become extremely difficult. Early & continuous observability is the secret sauce for delivering & sustaining a fault-tolerant reliable and high available system. Observability is a property and key characteristic of a modern IT system to expose details on the internal state of the system by generating external data such as metrics logs events & traces. An Observability tool provides the ability to collect real-time data monitor correlate analyse and visualize the hotspots to enhance the end-to-end visibility of the entire IT landscape. An Observability tool forms a vital toolkit for performing early Performance engineering and Chaos engineering as part of the CI/CD pipeline. This helps in adopting ‘Fail-Fast’ delivery culture by facilitating early feedbacks to development team and comply with Non-Functional Requirements (NFRs) of the system. Continuous monitoring of the Service Level Objectives (SLO) Service Level Indicators (SLIs) and Error budget is essential to control the velocity of the releases against the system reliability. A robust observability solution helps with monitoring of system availability and provides the ability to drill down and troubleshoot the issues. This helps in reducing the Mean Time to Detect (MTTD) and Mean Time to Resolve (MTTR). Thereby observability solution becomes crucial to meet the high availability targets and enhancing the customer experience.
