![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
testing DW
Sep. 2nd, 2009 02:51 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
szabgabIn the past few days I managed to fix some of the unit tests and set the rest to be skipped so once my latest patch of bug 1721 gets applied all tests in t/ will either pass or skip.
In order to make development easier in DW it would be important to keep the test suit intact and even adding more tests.
Currently the way to run the tests is by typing
cd $LJHOME
prove t/
In case you would like to run a single test file you can type
prove t/userpics.t
A better way to run the tests will be to run
prove -w t/
but currently it produces lots of warnings, something we should fix soon.
Every time to make a change you should at a minimum make sure that all the tests still pass after the change. If some of the tests stop working you should check if the test is incorrect or if the change you made to the code introduced a real bug and fix it.
( Details )
In order to make development easier in DW it would be important to keep the test suit intact and even adding more tests.
Currently the way to run the tests is by typing
cd $LJHOME
prove t/
In case you would like to run a single test file you can type
prove t/userpics.t
A better way to run the tests will be to run
prove -w t/
but currently it produces lots of warnings, something we should fix soon.
Every time to make a change you should at a minimum make sure that all the tests still pass after the change. If some of the tests stop working you should check if the test is incorrect or if the change you made to the code introduced a real bug and fix it.
( Details )