A reasonable approach to test company’s business critical information systems such as ERP depends on the visibility to product development. If the system is developed in-house there's likely a good visibility to actual development teams’ work and quality assurance can be involved in the very early phases of product development. Involving QA early can be referred to as shift-left. On the other hand, a system used as a cloud-based Software-as-a-Service (SaaS) without any visibility to development is restricted also from the testing point of view. Only production version testing might be possible, often referred to as shift-right.
Even in the best of times, we are constantly being asked to deliver more for each dollar in our budget while simultaneously maintaining existing output. Here are a few tips and tricks to help you stretch your IT budget in 2019.
Expanding the use of test automation beyond standard release pipelines to include security testing can offer major benefits. The question is, how can we integrate security testing into the software development life cycle?
A while ago I ordered some pizza online – well 41 pizzas, to be exact. The process was smooth: open a mobile app, choose the products, transfer to shopping cart, fill in delivery details, contact info, and credit card data, click “Pay now”. Then something really odd happened: I saw an order confirmation flash on the screen but in a couple of seconds it was blotted out by a big, red “payment refused” message. At the same time, my email inbox notified me I had a new message. The message said my pizza order was received and confirmed. Was it, really? I needed to feed 40 hungry people.
Are you struggling to get all your code released? So are many others. The solution may be hiring a robot – a QA robot!