Remove run fast tests, as this isn't really useful anymore

doc/concrete_syntax.rst

@@ -1,25 +1,8 @@
 Concrete Syntax
 ===============
 
-Explain concrete syntax and why we want to have it
-+ refer to paper
+Concrete syntax is an unavoidable aspect of modelling if you want to have decent usability.
+However, as the Modelverse is only a back-end, we leave concrete syntax up to the front-end to specify.
+Nonetheless, we have described and implemented a relatively simple way of supporting flexible concrete syntax, in an explicitly defined way.
 
-Defining Concrete Syntax
-------------------------
-
-Explain how we define concrete syntax in the Modelverse
-
-MM_Rendered
-^^^^^^^^^^^
-
-Explain how MM_Rendered looks like and what it can be used for
-
-Modelverse Client
------------------
-
-Explain the simple client, and why it can be minimal
-
-Modelverse Perceptualization
-----------------------------
-
-Explain perceptualization and how it communicates with the Modelverse
+TODO

doc/conformance.rst

@@ -1,19 +1,23 @@
 Conformance
 ===========
 
-Explain the conformance relation in the context of the Modelverse
+The conformance relation takes a central role in the Modelverse.
+In contrast to most other tools, the conformance relation is, as all other things, explicitly modelled.
+As such, it can be altered quite easily and offers many degrees of flexibility not found in other tools.
+
+Many of these dimensions, however, are still work in progres...
 
 Multi-Conformance
 -----------------
 
-Explain the notion of multi-conformance and why it is useful
+TODO
 
 Metamodel Finding
 -----------------
 
-Explain why we can do metamodel finding, and why we would like it
+TODO
 
 Conformance Bottom
 ------------------
 
-Explain the use of conformance bottom, and how it contributes in combination with metamodel finding, or finding a binding
+TODO

doc/scripts.rst

@@ -76,3 +76,12 @@ Run the tests for all parts of the Modelverse.
 Invocation::
 
     python scripts/run_tests.py
+
+run_basic_tests.py
+------------------
+
+Run the relatively fast tests for the Modelverse.
+
+Invocation::
+
+    python scripts/run_basic_tests.py

doc/services.rst

@@ -173,3 +173,13 @@ Also, by using external services, it becomes possible to rely on trusted parsers
 
 Users of the *compile_code* and *compile_model* functions are never exposed to the use of an external service: it looks exactly like any other function call.
 Nonetheless, there is a small difference: when the external service encounters a problem, or is simply not running, the functions will not be able to operate, even though the input is correct.
+In any case, the compile_code and compile_model operations return the root element when they encounter a problem.
+This problem could be anything, such as a syntax error or a semantical analysis error.
+Otherwise, the functions return the action language function and model, respectively.
+
+Before you can execute these functions, the HUTN compilation service must be running, which can be done by executing::
+
+    >>> python scripts/HUTN_service.py
+
+The service will connect to the Modelverse specified in its configuration (i.e., the *init* call).
+It stays connected until the *STOP* input is given on *stdin*.

scripts/run_fast_tests.py

@@ -1,10 +0,0 @@
-import subprocess
-import sys
-
-subprocess.check_call([sys.executable, "-m", "pytest"], cwd="state")
-
-subprocess.check_call([sys.executable, "-m", "pytest"], cwd="kernel")
-
-subprocess.check_call([sys.executable, "-m", "pytest"], cwd="interface/HUTN")
-
-subprocess.check_call([sys.executable, "-m", "pytest", "integration", "-v"])