Group items tagged

Filter: All | Bookmarks | Topics Simple Middle

shared by Sarah HL on 29 Jun 09 - Cached

They effectively communicate in an executable format how to use the software. They also prevent tendencies to over-build the system based on speculation. When all the tests pass, you know you're done!
...

Cancel
Test-driven development is a lot more fun than writing tests after the code seems to be working
...

Cancel
Do I have to write a test for everything? No, just test everything that could reasonably break.
...

Cancel
...6 more annotations...
If something is difficult to test, it's usually an opportunity for a design improvement.
...

Cancel
Frequent testing gives you confidence that your changes didn't break anything and generally lowers the stress of programming in the dark.
...

Cancel
Run all your unit tests as often as possible, ideally every time the code is changed
...

Cancel
For larger systems, you may just run specific test suites that are relevant to the code you're working on.
...

Cancel
write a failing test that exposes the defect. When the test passes, you know the defect is fixed!
...

Cancel
Don't forget to use this as a learning opportunity. Perhaps the defect could have been prevented by being more aggressive about testing everything that could reasonably break.
...

Cancel

shared by Vernon Fowler on 26 May 13 - No Cached

shared by Vernon Fowler on 06 Feb 12 - Cached

Start by creating an "assets" directory in the root of your SVN checkout. This will be on the same level as /tags and /trunk, for example. Inside that assets directory, you can make a file named "banner-772x250.png" or "banner-772x250.jpg". The image must be exactly 772 pixels wide and 250 pixels tall.
...

Cancel

shared by Vernon Fowler on 11 Jun 14 - Cached

yourls.org/#FAQ

shared by Sarah HL on 26 Apr 11 - No Cached

1 - 5 of 5

Showing 20▼ items per page