Answer the question
In order to leave comments, you need to log in
How to build a process of constant A / B testing of the site interface for the stream and not get into a puddle?
There are online stores, there is a business owner who wants to get feedback, have the best of Amazon, etc., at 1000 times lower IT costs than those he looks up to.
How to organize constant testing of the interface with a very truncated team? - SEO, two programmers, content manager. There are examples of friends who are constantly working on tests and experiments to modernize the interface with an increase in conversion, but there are almost two dozen interested people working on it, plus external departments are connected.
Is it possible in my case to somehow try to implement this? We do not have a business analyst and marketer.
Answer the question
In order to leave comments, you need to log in
First you need to formulate why you need automation and what you need for this.
> seo + 2 programmers
Well, ask your programmers if they can handle it at all. Maybe they don't even have the right skills?
With such a staff, I would break the task into pieces:
1. Figure out what kind of software is generally needed to build and launch a new instance of the site in your case. (DB, web server, etc.)
2. Write scripts for rolling them out.
3. Start writing tests.
For existing features, it is better to do functional (aka browser tests), because with them you can cover more code with less and accurately close the main work scenarios. (At this moment, you need to once again ask your programmers that they are capable of doing this - it may well be that there is no such thing, and then you will either have to invest in training or hire automation QA)
4. Raise teamcity or something similar. Let him now start it all himself.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question