In any software project, quality assurance is very important and of course, applications that live in the Episerver marketplace are no exception. This not only reflects the quality of the product but also helps the customer trust in who developed it.
For Episerver, add-ons quality assurance does not become of secondary importance. In order to modules can be published to the market place, they are examined carefully until no critical errors are found. The process from the add-on creator is simple. First, we generate and submit documentation of our module that will be used as a reference for the QA department to begin testing. Some of these documents are Installation and Configuration, Verification Guideline, User Manual, and so on. A couple of days later, you will receive an email indicating the errors found along with the level of affectation that can be critical, moderate and low. Critical errors must be fixed if we want our module to be published in the market place. The detail in the documentation provided by Episerver is really good. In it, we can find how to reproduce the issue step by step and some times we have screenshots or videos. In addition, they set up a QA environment where our module is installed, so we can reproduce the issue easily.
After having built several modules for the market place, we can recommend following the steps below when building add-ons to improve the time they are published. These steps are:
- Only users with the role of Admin should be able to access the module (unless your requirements specify a different approach).
- If you have search fields, make sure your module works when a user enters something like “<script>test</script>”
- Make sure you don’t have script errors. Look for errors in the browser console window.
- Create a confirmation message when an item is deleted.
- The module must be tested in the latest Episerver version.
- Make sure you provide the .Net framework version and Episerver version that you are looking forward to this add-on to work on.
- Do not allow duplicate names when creating items.
- Test your module using different languages.
- Uninstall the module and check that it was removed from Episerver.
Recommendation: To make the QA phase easier, make sure you test your application/add-on thoroughly before submitting the app to the Episerver QA team. This will save you and Epi team a lot of time with back and forth communication.
No model set
at Glass.Mapper.Sc.GlassHtml.MakeEditable[T](Expression`1 field, Expression`1 standardOutput, T model, Object parameters, Context context, Database database, TextWriter writer) in c:\TeamCity\buildAgent\work\8567e2ba106d3992\Source\Glass.Mapper.Sc\GlassHtml.cs:line 589