Developing test framework from scrach
Resently I joined a small software company to build auomation framwork for regression testing. TC was selected tool. There was no proper testing was implimented at there. But found lot of DUnit testin...
Forum Discussion
Hi,
> But found lot of DUnit testings were written without documentation and cover considarable functional tests.
May I wonder why do you think that the existing tests cover something if they are not documented?
Is it just because you was told this? Any reason to trust this? (The situation is exactly like with the regression testing you are trying to automate - you do not trust developers that nothing was broken and need to verify this.)
Also, even if the existing tests were verifying something when been created, do you have any reason to believe that the tested functionality did not change and existing tests are still relevant?
If your answers to the above questions are positive, then you may reuse existing tests and you should know what they do.
Otherwise you need either analyse them and figure out what they do and decide than whether this or that test is still valid and can be reused or should be abandoned and recreated, or, if you estimate analysis stage as too resource consumimg, just forget about existing tests and create new tests according to the requirements.
> But found lot of DUnit testings were written without documentation and cover considarable functional tests.
May I wonder why do you think that the existing tests cover something if they are not documented?
Is it just because you was told this? Any reason to trust this? (The situation is exactly like with the regression testing you are trying to automate - you do not trust developers that nothing was broken and need to verify this.)
Also, even if the existing tests were verifying something when been created, do you have any reason to believe that the tested functionality did not change and existing tests are still relevant?
If your answers to the above questions are positive, then you may reuse existing tests and you should know what they do.
Otherwise you need either analyse them and figure out what they do and decide than whether this or that test is still valid and can be reused or should be abandoned and recreated, or, if you estimate analysis stage as too resource consumimg, just forget about existing tests and create new tests according to the requirements.
