Last month I blogged about the addition of micro-iterations in endurance tests. I was never 100% happy with the name for these, and although ‘micro-iteration’ is a good description of what’s happening (it’s a loop within a loop) it’s difficult to say, and can be difficult to clearly identify when you’d use them.
During a between session chat with Geo Mealer during the recent QA Automation Services work week, he suggested calling these ‘entities’. This is perfect, because the purpose of these inner loops is to allow an endurance test to interact with multiple entities rather than just one.
The simple example is the new tab test, which opens multiple new tabs. In this case, the tab is the entity. A more involved example is the in-progress app tab test, where a tab is still an entity but we interact with it in multiple ways. First, we open the specified number of tabs, then we pin them all, then we unpin them all.
The rename has now landed, and documentation has been updated. From the perspective of writing tests nothing has changed, the only changes are the name of the command line argument and the method names in the endurance.js shared module.