I am a
C# developer, and my team and I are trying to start
automated functional tests. (Note that we don't want to do
Unit Tests; we expect to develop tests which test one function point per test)
Our software has several modules, but they have something in common: one input (can be File, string or database row) and some outputs (a file, a database row, or both in some cases).
One problem is that the configuration is stored in the database, and there is A LOT of configuration to enable the software to run correctly, and someone could change it and affect the tests.
In my opinion, we have an amazing Test team, and I'm thinking of finding a way where the developers could develop the tests but the Test team would sometimes help developing them too.
- The Test team develops the automated tests based on their test cases - is that a good approach?
- I know that if the creation of the test scenarios is hard to do, then the Test team will not see any reward. So, what's a good approach (in
C#) to develop automated tests where both teams (development and test) could help to improve them?