Testing new package before uploading to review
Permalink
I'm developing new package for Concrete5 and i'm using Cloud9 with latest Concrete5 version installed for coding and testing. After uploading my package for review i have recived a lot of messages about errors from reviewers. But this errors not occured when i tested this on my environment. So, how you guys test your packages before uploading to review?
My checklist is attached. While it concentrates on blocks, a lot of it applies generally.
Very little of this is my own work. Primary credit goes to MrKDilkington.
Very little of this is my own work. Primary credit goes to MrKDilkington.
What type of errors are being reported?
Here are some useful links about marketplace testing:
https://github.com/katzueno/concrete5-prb-checklist...
https://legacy-documentation.concrete5.org/tutorials/get-an-addon-or...
http://www.concrete5.org/developers/submitting-code/marketplace-sub...
https://www.concrete5.org/community/forums/submitting-to-the-marketp...
I would also add that testing using multiple browsers, multiple versions of browsers, across multiple operating systems is very useful. This can be done using a virtual machine and/or services like BrowserStack.
Setting your database to be strict is also helpful.