Don't write a load of code and then hand it over to the testers and say "i think it works" and put responsibility on the testers as to whether or not release your stuff. Test it to F. Then hand it over. Know it works. Be responsible.
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Expensive contractors, take responsibility for your work!
Collapse
X
-
-
So you're on a tulip rate/salary I take it?Originally posted by aussielong View PostDon't write a load of code and then hand it over to the testers and say "i think it works" and put responsibility on the testers as to whether or not release your stuff. Test it to F. Then hand it over. Know it works. Be responsible.Hang on - there is actually a place called Cheddar?? - cailin maith
Any forum is a collection of assorted weirdos, cranks and pervs - Board Game Geek
That will be a simply fab time to catch up for a beer. - Tay
Have you ever seen somebody lick the chutney spoon in an Indian Restaurant and put it back ? - Cyberghoul -
So you also think testers are a waste of space?Originally posted by aussielong View PostTest it to F. Then hand it over. Know it works. Be responsible.Comment
-
No don't. Just hand it to me and let me send an invoice for testing it.Originally posted by aussielong View PostDon't write a load of code and then hand it over to the testers and say "i think it works" and put responsibility on the testers as to whether or not release your stuff. Test it to F. Then hand it over. Know it works. Be responsible.And what exactly is wrong with an "ad hominem" argument? Dodgy Agent, 16-5-2014Comment
-
Testing is for girls.Originally posted by aussielong View PostDon't write a load of code and then hand it over to the testers and say "i think it works" and put responsibility on the testers as to whether or not release your stuff. Test it to F. Then hand it over. Know it works. Be responsible.You can lead a fool to wisdom but you can't make him think.Comment
-
I wrote it to spec. I tested it to spec. Just because the spec doesnt match the requirement is not my fault.Originally posted by aussielong View PostDon't write a load of code and then hand it over to the testers and say "i think it works" and put responsibility on the testers as to whether or not release your stuff. Test it to F. Then hand it over. Know it works. Be responsible.
I will gladly fix the requirement, spec and code so that it actualy works, but it will cost you.I am not qualified to give the above advice!
The original point and click interface by
Smith and Wesson.
Step back, have a think and adjust my own own attitude from time to timeComment
-
It certainly pays for Mrs Tester’s shoe collecting habit.Originally posted by Amiga500 View PostTesting is for girls.And what exactly is wrong with an "ad hominem" argument? Dodgy Agent, 16-5-2014Comment
-
http://en.wikipedia.org/wiki/Test-driven_development
Code shouldn't be part of the build until it has passed all of the test cases. Only then does it get to the deploy and test phase.
HTHComment
-
Shirley?Originally posted by Mich the Tester View PostIt certainly pays for Mr Tester’s blowjob habit.Comment
-
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers

Comment