Full QC on the plugin features.
smileBeda opened this issue · 1 comments
A full QC (Quality Control) is required on the plugin.
This means, install the plugin on a fresh CP install, use its feature, like a new user.
Report back issues to the repo, separated in tickets, either of type Bug or Usability issue depending on what was found.
QC is not used for detecting missing features, but only to test the quality of the product as is.
If a feature should be changed to improve usability that is a valid request, but adding features, just because, is not.
Everything goes into a QC aspect, from typos up to broken things.
After each fix, the QC needs to be repeated for that aspect.
I have used this extensively and made a bulk of changes due to usage thus we could say a first QA was done, but it had so many changes as consequence that doing a QA at this point is meaningless.
Currently the plugin won't work as standalone due to having added Search and Filters which required a different resolving of ShortCodes.
Until conditional shortcode is not moved out of the basic plugin, they plugins have to be used together.
That is unsuitable for a QA thus closing here.