Press "Enter" to skip to content

Posts published in “Experiences”

What is Experience Based Testing in Agile projects?

Vladimir Simonovski

Meaning There is no formal definition of what experience based testing in Agile-oriented projects is but to put it in simple terms, it’s testing a product using your previous experience. As the name implies is a testing activity performed by the QA based on the experience gained through the years on each project iteration. Verification of the quality of the product using the experience from previous projects, approaches, business domains, organizations, etc. Since it is done often due to the…

Top 8 test automation criteria you need to fulfill

Vladimir Simonovski

Most organizations today are striving to develop automated test cases but not all do so. Manual test cases are mostly something they start to create especially when the project is started from scratch. When the time comes to migrate towards automation, we need to re-evaluate the state of the already written manual test cases and choose which of them can be converted into automated tests, which can be removed or new ones may be developed to cover the removed ones,…

How important Software Testing Life Cycle is?

Vladimir Simonovski

What is STLC? STLC is a process of actions that are performed(followed) during the testing phase in order to satisfy the end goals. This includes testing all the happy flows and edge cases, ensuring the overall quality of the product is met. STLC is part of SDLC but focuses on the testing activities that start right after the requirements are defined by the customer. Why do we need to establish STLC? It is always better and cheaper to prevent a…

How requirements engineering can help us clarify and understand customer requirements?

Vladimir Simonovski

When it comes to working in Agile development, teams are working together with the customers throughout the software project. They’re constantly communicating, collaborating, and exchanging ideas and suggestions for product improvement. Usually, the customer requests a new software functionality, and together with the agile team, that functionality is converted into a form of a requirement. That requirement must be clear and concise so that everyone can understand what is the purpose. Out of the requirement, epics and user stories are…

What makes for a good Acceptance Criteria in Agile Projects?

Vladimir Simonovski

Many organizations today are clearly focusing on having often software releases to the client. Even though the software is with reduced functionality, it is still available early in the development lifecycle and has a time-to-market advantage. Usually, the organizations are following the agile way using SCRUM for delivering software where every functionality is captured by writing user stories in a collaborative way between the members of the team. For the user story to be fully developed, tested, and integrated with…