Automation is everywhere. Automation experts are in high demand. Nah! Not in high demand, ONLY Automation Engineers are in demand. All job descriptions mention a set of automation tools and frameworks. Interviews revolve around Java, Python, C#, Selenium, UFT, Appium, Frameworks, Algorithms, and what not. Literally ‘Everybody’ is looking for an Automation engineer.
Micro Management kills the trust. Or it proves that there is no trust at the first place. And Freedom breeds innovation. It is when you give people the power & the freedom that ideas originate. And one out of five/ten ideas works out to be superb. It is when you trust in your team that they perform. When they know you are backing them. You believe in them & in their work. In their potential. A strong manager have full trust is his/her team – it is about the tasks, work and the value-adds, innovation. It is not about ‘controlling’, it’s about ‘managing’. Ever had a micro-management incident in your team? How did it impact the team morale? Or how a strong manager built the trust & team pulse?
I assume ‘every’ fellow Tester in my network have experienced this situation at least once in his/her career. One of the most common Testing situation – How do you handle timeline crunch? Since Testing is the last step before client demo, the Test team has to make-up for the delays encountered till the build is deployed in Test environment. Now how do you handle crunch timelines without impacting the quality?
Communication is important. “Excellent Communication Skills – a must” is always one of the Job descriptions. If not explicitly written, it is implicitly understood. One of the most important qualities recruiters look for in candidates is their ability to communicate clearly. You might be technically good, but you don’t work in silos. People work & achieve as a team. Communication is not just about the language but putting across your ideas in a simple manner, clear in understanding.
Some say serving notice is just like your ‘honeymoon period’. Is it because you are leaving the firm and no more accountable? Or why put efforts for something you know is soon going to end? Coming late – Going early becomes normal? Why?
Many a times we face these kind of one-off bugs 🙁 which peep-out and then hide somewhere. “It was a one-off bug and now not reproducible – so what can I do?” Wrong! Though one-off but still it is present somewhere in the software and as a Tester it is our responsibility to investigate it. How?
Yeah! Today I am resigning from my current organization. Often asked about ‘Why are you leaving your current Organization?’ – I feel there is no single reason. Leaving a company which has been your half-home for years is a professional as well as emotional decision. It’s an important decision which can be (& mostly is) a result of multiple factors,
FinTech, a buzzword today. Though it has been around from the start of 21st century, recently it has gained unprecedented momentum. Why? Due to the emerging disruptive technologies. But what exactly is FinTech? And how it should be perceived as a Tester? What’s the role of a FinTech Tester? What’s the scope of FinTech Testing? These are some of the doubts testers working in the Finance domain come across daily. This article tries to answer these questions in simple terms. The Finance. The Technology. What’s FinTech? The role of a FinTech QA. And its scope. Let’s deep dive…
Any technology or tool is worthless unless it is being used by ‘some’ organization somewhere. It all starts from organizations adopting the new technology or a tool and then it gets popular slowly. In that sense QA Job Descriptions are a great source of current technology, i.e. practical tech. being used by IT organizations. Be it Selenium, Protractor, Appium, API tools, Big Data Testing, etc. Everything is embedded in the QA Job descriptions, you just need to mine some data 😉 But don’t worry. Software Testing Studio has started a new series for you – “JD Talks” where we mine hundreds of Job descriptions to come up with latest tools, technology, languages and concepts. Let’s see what the first set of JDs talk about…
Multiple Operating Systems, Devices, Network operators and interfaces increase the risk of failures, if not tested properly. Keeping in mind the permutations & combinations involved in App testing, let’s try to answer the basic question – Test Coverage – or the types of testing required to get that awesome App experience.