A lot of factors impact the speed with which you can execute an optimization testing campaign: the complexity of your tests, the expertise of your team, the desired statistical significance of your results, and more. One factor that’s often overlooked, however, is the organization of your testing workspace.
A testing workspace is the campaign dashboard developers use to configure test campaigns and establish the settings of those campaigns. It can be challenging to keep a workspace organized because people with different roles and backgrounds will use it, including marketers, data analysts, and quality assurers. But an organized workspace helps everyone work more efficiently, which makes it easier and faster to launch campaigns.
As a Solutions Engineer at Oracle’s Maxymiser, I recommend anyone looking to improve their workspace organization develop a good, consistent naming convention. This will encourage people who use the testing workspace to give all objects in the workspace names that indicate the objects’ purpose.
Developing a Naming Convention
A brief reminder: Everything stored in a workspace is an “object.” Objects can be tests, scripts, metrics, pages, test elements (and their variants, which are different versions of those elements), and more. To tidy up a workspace, create ground rules for naming the objects inside it that apply to everyone, no matter their job title or department. Vendors should follow the rules, too.
Here are my 10 main pointers for developing a great naming convention:
In addition to following the above tips, regularly go through your workspace and audit the usefulness of the objects there. Delete old, unnecessary objects to further cut down on confusion and clutter in the workspace.
Moreover, when you create objects or publish updates, use the provided text space to describe the object’s purpose, any changes you've made, and why you made those changes. Keep it short but make sure it’s clear. This, for example, is an excellent publishing comment: “Added a page to represent the cart page for T23. Pushing it live as part of T23’s launch.” Over time these descriptions will build up to form a record of everything that’s been published, which will help developers as they build more objects in the workspace.