How to force developers to hand over a tested product?

andreevich2012-02-02 19:43:15

Software testing

andreevich, 2012-02-02 19:43:15

Good evening!
My Mrs. the office orders software from a third-party, which is a monopolist in this area. Recently, these comrades began to hand over to us, such a feeling, a completely untested version of the product. In this connection, you have to spend a huge amount of time testing those aspects of the product that were not affected in the version update (they should not have been).
As a result, it turns out that I have to be their tester, sending error reports (and errors are sometimes banal: either the button does not work, or the field is inactive, or selects from non-existent tables), but I only have to check compliance with the stated requirements of the technological setting.
I heard that there are all sorts of “unit tests” and so on, that the process can be automated at the development stage.
Maybe there are some reports of test methods that will confirm the work / testing done or something else?
How can you check that the product has been tested and that it (not) passed successfully?

Software: a set of server applications in С++/#, MSSQL

Thank you for your attention!

Answer the question

In order to leave comments, you need to log in

7 answer(s)

Anatoly, 2012-02-02
@taliban

1. Talk to your boss about fines for holes (fixing is free, etc.)
2. Change the price without taking into account testing and hire separate testers
.

un1t, 2012-02-02
@un1t

Unit tests are great, but they don't remove the need for acceptance tests. In addition, writing unit tests is a secret knowledge that is transferred only from developer to developer and is practically not disclosed in the literature. Most developers don't write tests simply because they don't have these skills.
If you hire a tester, he can test the functionality manually and write automated acceptance tests. Of course, such work should be done on the side of the developers, but since everything is so sad there, you might think about competent testing on your side.

EndUser, 2012-02-03
@EndUser

The contract had to be written correctly, with a carefully prepared chapter “acceptance procedures” and “penalties”.
Now it is already very difficult to beat an unscrupulous programmer.
For now, click on the compliance with the TOR, if at least someone there guessed to write “the system must perform a function”, and not “the system must have a function”
And along the way, write in a notebook the wording of the contract for the next stage (and other future projects).

Dmitry Bykadorov, 2012-02-02
@hudson

There is such a thing as acceptance testing (such as state acceptance) by the customer (you). If the software has bugs, then it is better at the performer's stand (before installation in production). If acceptnace fails, the software is for revision. Poidee under a contract with state structures, this should be stipulated.

egorinsk, 2012-02-03
@egorinsk

You can try to delay funding in proportion to the loss of time for improvements and corrections, if payment is made in stages and there is such an opportunity. That is, due to minor bugs, you do not accept the next stage and delay payment.

Mark, 2012-02-02
@printf

Answering the question
> How can you verify that the product has been tested
No way, you can only speculate.
Everything was written correctly above, plant testers at your place, and deduct their salary from the order amount.

LeoCcoder, 2012-02-02
@LeoCcoder

Find a serious developer who won't try to sell you a bad program.
Ask what methodology they work with, what percentage of code and functionality is covered by tests, talk to customers who have already worked with this office.
You can introduce fines/bonuses for bugs, but this will not solve the problem at the root. If the office is worthless, then it suddenly will not become good.