How does Contract Software Testing work : as a perminant employee I can test software and give recommendations but it's an art not a science. Full testing is impossible unless you have a ridiculously simple system so there are always issues missed by testing/QA and potentially live issues as a result. (Two testers could test the same system and come up with two sets of bugs/issues...) - How do seasoned contract testers feel about this and how they find their contracts/work out in practise? - In many organisations, testers are come under fire from project teams and are sometimes held up as scapegoats for project issues (last minute changes rushed through with no time for reasoned regression testing etc).
Is contract system testing any worse than perminant and are there any particular issues with contract testing that perhaps don't apply to other roles? I could envisage that testing is perhaps more risky than say programming from a blame/liability perspective?
Is it just a case of phrasing the contract to reflect that services are offered on a best endeavor basis and specifically exclude any liability for direct or indirect losses/consequential losses arising from the services provided in addition to taking out the necessary PI and limited company setup?
Is contract system testing any worse than perminant and are there any particular issues with contract testing that perhaps don't apply to other roles? I could envisage that testing is perhaps more risky than say programming from a blame/liability perspective?
Is it just a case of phrasing the contract to reflect that services are offered on a best endeavor basis and specifically exclude any liability for direct or indirect losses/consequential losses arising from the services provided in addition to taking out the necessary PI and limited company setup?
Comment