Press "Enter" to skip to content

Posts tagged as “Software Project”

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 continuous testing affects continuous integration and deployment?

Vladimir Simonovski

What is Continuous Integration (CI)? To put it in simple words, it’s an action where developers are integrating code into a shared repository preferably, multiple times per day with the goal of finding errors quickly, providing fast feedback on the quality of the code, and executing an automated build to show the current state of the system. Continuous testing or automated testing is not part of CI but it’s usually paired together in order to discover the presence of bugs…

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 to ensure that a Risk-based Testing strategy is implemented correctly?

Vladimir Simonovski

What is Risk-based Testing? As the name suggests, Risk-based Testing is a form of software testing that is based on risks. Since the risk is a potentially negative outcome of a functionality, Risk-based Testing covers the one with a higher chance of failure. Risk-based Testing must be defined at the earliest stages possible when customer requirements are defined in order to reduce the potential number of errors in the later stages of development and to guide further planning, implementation, and…

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…