This is one of the most common questions discussed among the Agile Community – What happens with the undone User Story of Current Sprint? Why does this happen? How should you deal with the undone user story? What should become of such stories? What should be done with the product backlog item itself? Should be it split or should it be carried into the next sprint? Should the team receive any velocity “credit” for completing a portion of the story? And how do you prevent it from happening again? This article addresses all of these questions.
Agile software testing is the requirement of a modern software development team. Choosing agile testing tools is not an option anymore, it’s a necessity. If you want the end product to be effective, speedy and sustainable simultaneously, you must go with a tool which provides agile testing solutions under a feasible budget.
Definition of done is one of the Agile fundamental things. Yet many teams do not see its importance or are unsure what Definition of Done actually is. The term is also often confused with the acceptance criteria, leading to mis-communications and false expectations. So, let’s have a look at this important agile concept – the definition of done.
Recently I am observing a rise of API Testing in the Job descriptions. I once did Web Services testing using SOAP UI testing tool, i.e. verifying the XML request-response. Thought it would be a good time to refresh the concepts. Anyways it was on my list since I started STS. When we look at the Software Testing trends, API testing is rising in priority & relevance. Let’s deep dive into the world of API Testing…
A peculiar but prominent distinction – Technical vs Domain Tester. Yeah! We know both are necessary for a successful QA career, but after certain years of experience your resume tend to incline towards one or the other. We are not Rajinikanth after all Who wins the Technical vs Domain Tester battle? Nah! It’s not a comparison between Deepanshu and Kanchan (we are together after all ;-)) but comparison between two different kinds of resume!
Too much work, every day we stay late in office. Oh it just skipped my mind, sorry. Let’s discuss it tomorrow. His/her mail is always ambiguous, let’s discuss on call directly. They are discussing about the technical design, we (testers) need not attend. Hey developer – have mailed you the bug, please investigate. These are some of the common dialogues in our everyday IT life. Ever thought of changing something? Nah? Yes? Every one of us notices something errant but then forget about it the next moment. But we say – Small changes can make a big difference to your career.
Every other software (or product) development firm is facing a tough competition in getting new business. Millions are spent on the marketing strategy to lure customers into signing contracts. Every day new marketing ideas pop up, a new strategy is formulated, costs are brought down, processes are being automated, social media & optimization are being exploited, different tools like Marketing Cloud are implemented, and what not. Marketing has grown into a multi-million $ industry in order to bridge the gap between companies and the customers. In all this hunky-dory picture, we are neglecting the most effective marketing tool available to all. Let’s explore…
Enterprise mobility solutions can present a number of challenges – Mobile governance, or the Management of people, policy, and process issues. At times it can seem like a minefield, but enterprises can quickly identify these challenges and overcome them in order to deploy an innovative enterprise mobility strategy. Companies need to bring all stakeholders into the fold to create truly productive and effective Enterprise Mobility. Here are the key challenges that organizations face as they define their Mobility strategy.
Recently our article “Manual Testing Is NOT Dead, But Manual Testers Are!” got major traction on social channels and triggered a debate in the Testing community. Some say “I have been doing Manual Testing since a decade now, and I am alive” while others approve of the title. Whatever be the debate (or discussion), Manual testers are finding it really tough to cut through the current jobs market. Want a proof? Try an experiment by analyzing the humongous response to a job opportunity posted for Manual Testers with 3-8 years of experience. How to move forward in Software Testing career?
James Bach. What comes to your mind when you hear the name? Disruptive & Controversial Tester. Founding member of the Context-Driven School of Software Testing. Creator of Rapid Software Testing™, Session-Based Test Management, and one of the progenitors and advocates of skilled exploratory software testing. The original buccaneer Tester. His thoughts are revolutionary & an inspiration to both entry-level & experienced testers. He is straight-forward & fearless in advancing the Software Testing technology. James Bach is synonymous with testing, and has been disrupting the industry and influencing and mentoring testers since he got his start in testing over 30 years ago.
Purpose, noun, the reason for which something is done. Recently a discussion was started by one of the Testing co-blogger at LinkedIn “What drives Quality Assurance? What is the purpose of Software Testing?” A relevant discussion indeed. They say “If you’re not working with purpose, you’re doing it wrong.” This triggered me to put on the thinking hat and pen down my perspective of ‘Software Testing Goals’.
Defect Leakage is natural. It’s common. If you build a software, bugs will be there. Similarly even if you Test a software, you cannot prove their absence. But we can do our best to eliminate maximum of them. Typically in most of the projects even if you complete functional testing (system testing) without any time & cost constraints, still UAT team (Business) manages to catch some more bugs. Any idea why? There has to be something missing in the system test coverage. What is it?
From the time I am blogging, it makes sense to me to pen down my sudden thoughts. Many a times you come up with an idea, memory, solution, problem, anything and it is lost since we don’t remember it in future. That’s when I started writing my sudden thoughts about Software Testing and guess what, the ‘Sudden Thoughts of a Software Tester’ is getting a lot of traction on my Social profiles. So thought of sharing it with you all. Here we go…
Unless you took a refugee or voluntary retirement or moved to Himalayas, you must be aware of the ‘Virtualization’ and ‘Cloud Computing’ concept. Cloud computing has passed through the stage of hype to become a reality of modern enterprise infrastructure. Every other Tech giant has its cloud offerings, be it Amazon, Google, HPE, IBM, Microsoft or Salesforce. And how did it impact the Testing landscape? Yeah! Every big innovation in the technology space has its parallel influence on the Test processes & techniques. In no time testing evangelists started exploring the Clouds and came up with new Test approaches suited for the Cloud. Cloud Testing started trending in the town and I too jumped into this bandwagon. Yes, recently I have been working on a Salesforce Marketing Cloud project and OMG! Cloud Testing is so different..!