Added expected results to each example and modified the script to work with it
Joined the script into one and removed .txt files
The test seems to work with parallel process.
Rigth now the user must be carefull when using the script because the output file must be empty.

Tonight I will let the script working to check it results
The script already works with threads and give us the same results than the other scripts in a slower time
The script now uses subprocess instead of threads.
The script already test if we have a petri net or not.
right now the script only works if you execute it with argument --run and gives you, for each example, if it's a petri net or no.

The execute_test script writes EEC/TSI concludes * to indicate analyze_algorithm that it was not a petri net and these algorithms are useless
The script already lets you choose how many process do you want to execute in parallel

changed to shell=False.

I have found some problems while implementing this stuff:
* As I had kept the pipe to comunicate with the process, although the process had ended its work, it had became a zombie process. (I had a reference to the process so It was not deleted)
To fix it I create a dictionary to store the relation: file descriptor - subprocess pipe, and when the process ends I modify the information of the dictionary to: file descriptor - output given by the process; so I drop the reference to the subprocess and it is deleted so there are no more zombie
* Other problem was that when a process ends, if I free the fd associated to its output pipe (to let the process be eliminated by the garbage collector), another process can take the same fd number so the dictionary becomes useless.
The solution consists into take another dictionary and store in it the outputs of the ended processes, indexed by pid of the subprocess that generated it, instead of the fd
I have adapted the script to the simple version we were talking about on github. It's so much cleaner than the older version of the script.