Mnemonics for maven - three funny phrases to quickly remember what maven default lifecycle is

If you, like myself, often have to switch between different technical stacks, you may know what it feels like not to be able to recall something you put so much energy in just a little bit earlier. Time has come to do something about it.

As you probably remember maven supports three built-in lifecycles: default, clean and site. The latter two are more or less straightforward, but default one is not so. And today, tired of putting it off, I, finally, did these phrases to memorize phases of the defautl lifecycle.

Here they are:

Very Curious: This Parrot's Voice's Indefinitely Deep
Vault Closed To Put Valuables In Dens
Vessel Carries Ten Pink Velvet Ingenious Dogs

First letter of each capitalized word should map on this: Validate > Compile > Test > Package > Verify > Install > Deploy.

Of course, you still have to remember about goals and executions, not to mention the other two lifecycles and their phases, but that's the start.

Good luck.

PS: For more information on maven please checkout these:

• maven official
• brief but informative explanation of maven phases and goals

Build your own Goldberd machine: Selenium via SoapUI

NOTE: The code examples I refer to in this blog are no longer available, but you can still read the text

Hello, friends. Here is how you can have Selenium run from SoapUi Groovy script step. This solution was created and tested with:

• SoapUI 5.X
• Selenium 3.X

In brief, you need to

• upgrade the libs under $SOAPUI_HOME/lib (! not bin/ext)
• use a custom java library (goes under $SOAPUI_HOME/bin/ext)

Auxiliary materials.

Code examples can be found here. An example of a project with a Groovy script is inside the project under auxmaterials folder.

Total automation with sellotape and glue

Luckily for all of us every profession evolves, and test automation is no exception. What I can see is test automation is now more affordable, and is done in a more professional way than before.

Same goes for approaches and tools (and for those who still trust Internet more than their own judgement, some gurus have already posted a very good knock out article leaving losers like myself with a tingling feeling of guilt for being too slow to update the blog).

But there's still another subject I would like to speak about. It concerns the approach to automation in general. Actually, it intends to slightly shift the way we understand automation and targets some of the popular stereotypes in attempt to get rid of them.

Some ideas to help you explain to your project manager why things just do not happen by themselves

You can't always get what you want


Result is not something guaranteed, not something you can count on, no matter what. Result is something you can get, if you are lucky and all the conditions are in your favor, and you can focus, and you are prepared to invest some extra effort, if you, despite all the desperate measures, run out of your resource.

I observed that planning is often done without even attempting to check if the goal or its parts are really feasible. The industry seems to be forming this habit of not questioning the task unless problems are too obvious. They pay you for doing something. And that means there's no way back, because some other people have already committed to do it, so now you have to provide a solution to support their commitment.

This way of doing things is not very helpful when it comes to planning, especially if area is not sufficiently familiar.

Flow for Managers

There's no such a thing as a universal way to do your job and not let it kill you.

To achieve the best results some professions need to work in a flow, and some -- in a quick succession of tense-release phases. And, among other things, 'the result' is assessed by how much better your life has become (or maybe it took a turn for the worse).

It looks like Pomodoro-like techniques are best for managers who are forced to operate in a quickly changing environment, while flow is necessary for engineers and researchers.

QA Venn Skillset Maps

I would like to share with you this little trick.

I use it every time when I need to find out, how hard it would be to learn something new. You can use it for yourself or for your team members. There are a lot of situations when you may need it, for instance:
-- you are building a matrix of competence, 

-- or calculating the team capacity,

-- you are thinking about taking a different a job, 

-- or starting a new project and not sure if you are up to it,

-- or maybe you are hiring someone and need to assess their skillset.

Average QA expertise can be represented as a Venn-like diagram. As you can see, it consists of three major parts:

• skills related to the test itself (QA): such as QA theory, certain cognitive skills, decision making skills, logic in a broader sense;
• tools-related skillset (Tools): knowing our tools, whatever they are, from test management systems to programming languages;
• knowledge of the domain (Domain): dark secrets of this particular trade, be it banking, telecommunication or IOT.