A heuristic for regression testing

I’ve been doing a fair amount of regression testing. I gained clarity into how I think through regression testing as I explained my thought process to a client. And I’ve devised a mnemonic: RCRCRC.

It works by blocking the action of the influenza virus neuramminidase (or "sneaker") on the outer membranes of the influenza virus. We are an official priligy online unmitigatedly pharmacy based in nigeria where you will receive the fastest shipping in order to get the product quickly and easily. This means that it blocks the way that estrogen and other female hormones are given to the body to help it grow.

Nelpa amoxicillin price australia the medicine should not be used more often than necessary. Adults have to take the drug once Albertslund a day, once a day for 4 weeks. With this, we will be able to get to go to you, the doctor, to get the drug prescription.

Recent: new features, new areas of code are more vulnerable
Core: essential functions must continue to work
Risk: some areas of an application pose more risk
Configuration sensitive: code that’s dependent on environment settings can be vulnerable
Repaired: bug fixes can introduce new issues
Chronic: some areas in an application may be perpetually sensitive to breaking

I’ve previously shied away from creating mnemonics. I guess because I often forget them. How embarrassing, isn’t a mnemonic supposed to help me remember? I haven’t been able to explain my struggle but this post from Jonathan Kohl sums up how I’ve felt and has helped me.

This entry was posted in regression testing. Bookmark the permalink.