search

chintan39 / wildblog

Automatically exported from code.google.com/p/wildblog
Other
0 stars 0 forks source link

Autotest tool (15h) #153

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Design and implement simple auto testing tool, which can test the base 
functions of system.
* package and controller can define what to test
* standard success message or error string returned
* not clear it should be the part of the system or separate from the system 
(this case is better to find errors outside packages or even in syntax)

Original issue reported on code.google.com by horak.honza@gmail.com on 12 Feb 2011 at 10:26

GoogleCodeExporter commented 9 years ago 
What should be tested:
* write permission to all directories (that needs it) and write suggestions 
(selinux)

Original comment by horak.honza@gmail.com on 20 Feb 2011 at 11:36

GoogleCodeExporter commented 9 years ago

Original comment by horak.honza@gmail.com on 29 Sep 2011 at 10:59

GoogleCodeExporter commented 9 years ago 
How to use test package:
...in package:
bool BasePostPackage::testSuite() {
  $tmpPost = new Post(); $tmpPost->title="sdf"; ...
  BasePostsController::actionPost($tmpPost);
  $ret = TestSuite::checkSmarty("post->title", "sdf");
  return $ret;
}

Original comment by horak.honza@gmail.com on 29 Sep 2011 at 11:07

GoogleCodeExporter commented 9 years ago 
Base package checks directory access (create and remove tmp files, if old files 
have same user/permissions as the created one);

Original comment by horak.honza@gmail.com on 29 Sep 2011 at 11:09

GoogleCodeExporter commented 9 years ago 
If variables in templates are standard somehow, then same routines can be used. 
Also every package can provide action with some standard input, but not sure if 
it is worth.

Original comment by horak.honza@gmail.com on 29 Sep 2011 at 11:11

GoogleCodeExporter commented 9 years ago 
Issue 228 has been merged into this issue.

Original comment by horak.honza@gmail.com on 29 Sep 2011 at 11:12

GoogleCodeExporter commented 9 years ago 
Interactive tests will be only described.

Original comment by horak.honza@gmail.com on 1 Oct 2011 at 6:18

GoogleCodeExporter commented 9 years ago 
Tests should be in separate object and directory: 
packages/Basic/tests/BasicAutoTest.php
packages/Basic/tests/BasicInteractiveTest.php

Original comment by horak.honza@gmail.com on 1 Oct 2011 at 6:21

GoogleCodeExporter commented 9 years ago 
What to test:
messages
gallery, images
media manager
tinymce editor
db consistency

Original comment by horak.honza@gmail.com on 5 Oct 2011 at 5:10

GoogleCodeExporter commented 9 years ago

Original comment by horak.honza@gmail.com on 12 Nov 2011 at 9:13