Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Obsolete
-
Affects Version/s: Current Version
-
Fix Version/s: None
-
Component/s: OIOIOI
-
Labels:None
Description
Sometimes we update Vagrantfile, so it works, but later someone forgets to update it alongside with his/her change, so I wanted to suggest a nightly test which does vagrant up from scratch[1] and after a while checks some simple scenarios[2].
[1] Deletes previous VM and creates a new one installing everything
[2] User registration, contest creation, submitting some code, etc and checking the HTTP answers if it is really what we want and not some 500s errors.
[1] Deletes previous VM and creates a new one installing everything
[2] User registration, contest creation, submitting some code, etc and checking the HTTP answers if it is really what we want and not some 500s errors.
