The best way to test software

Question

I just finished (mostly) a large application that I worked on for a little over a year (incl.). This is about 86 thousand lines of code, of which 50 thousand are from the automatically created Visual Studio dataset. This is largely a graphical interface for interacting with a database, creating reports, etc. He deals with money and manages contracts, so it is important that he is as white as possible.

I went through the code and ran the program myself. I, for the most part, cannot find any more errors. However, I am sure that I have just worked on the system for so long that I can no longer see them. I know that there are some due to some intermittent problems that I encounter, but I can’t pinpoint.

How do I go through software testing to detect any remaining bugs?

Answer 1

I know this is a little late, but have you heard of Test-Driven Development ?

There are many tests you could build to detect the “remaining” errors:

1) Unit tests

2) Integration Tests

3) Behavioral / business / acceptance tests

You can always visit the Bootcamp Tester to get more ideas.

Answer 2

- . , , , .

Answer 3

Since you did not use TDD to record it. It’s best now to add as many automated tests as possible to cover common scenarios. Thus, when you find errors, and there are ALWAYS errors in programs, you can hope to minimize the risk to the rest of the system when you fix them.