# HG changeset patch
# User durandn
# Date 1427808776 -7200
# Node ID 018094c4045374a62250aa70da2c945512a9fdd1
# Parent  6c19ea70f056248872f768269d14a8f1feca5056
Edited Readme to include a testing protocol for CatEdit

diff -r 6c19ea70f056 -r 018094c40453 Readme.md
--- a/Readme.md	Tue Mar 31 15:04:40 2015 +0200
+++ b/Readme.md	Tue Mar 31 15:32:56 2015 +0200
@@ -65,3 +65,22 @@
 * "object_type" : "my-object-type",  -> either "literal", "uriref-category" or "uriref-link" at the moment
 * "rdflib_class" : some-RDFLib-concept, -> a rdflib class of some sort with its namespace, examples: SKOS.related or RDF.Type representing the predicate
 * "object_rdflib_class" : some-RDFLib-class:  -> a rdflib class representing the object, either Literal or URIRef
+
+## Testing Protocol for CatEdit (development) ##
+
+These tests are meant to be run alongside unit tests (that are not completely implemented yet) to test that everything (and specifically Javascript) works properly.
+
+Make sure to work on catedit-dev-testing-2, this repository is only used for development tests to reduce GitHub notification spam for other users. (For the record, catedit-dev-testing is used for other users to test CatEdit functionalities as a whole)
+
+Create and submit 3 categories: toEdit, toDelete, and doNotTouch. doNotTouch must have a "related to" property with "toDelete". Add at least one "link"-type property (resource for instance) and one "text"-type property to test if every type of property. Double-check with the property list in your config.py to check that every property appears on the editor and is correctly configured.
+
+Then, edit the toEdit category and delete the toDelete category. Submit changes and check that comment thread for your submission is created and detected by CatEdit. Add a test comment. Check that doNotTouch isn't related to toDelete anymore (as toDelete was deleted). Also check that the changeset comment thread page also shows you to the repository state before your changes, after your changes, and to all the changes you made.
+
+Create a discussion called "discussion test CatEdit dd/mm/yy" and add a test comment.
+
+Also test that the button "delete all changes" work properly.
+
+Test the javascript on Firefox, Chrome and Safari:
+* In the editor, the right fields are generated according to the property type, the property are added to the list when you click the "add property" button, and it is possible to delete each property separately
+* In every page that has a category list, the + and - button displays category details properly, and you can hide or show the whole table using the ^ button. The trahsbin and x buttons display a delete confirmation message with the button to delete category or change
+* In a changeset page you can hide and show the previous and current state of the category set, and you can hide and show the changes that were made.