Lately, the application of production, one of the parts of the protocol is being changed. Is it important to re-test the entire application or is it enough to just test the functionality associated with that part? Do you have any ideas about this?
Thanks.
It will be good if you test the entire production application, and not just the functionality so as to detect any errors that may be in the application and deal with the as soon as possible. I will suggest that you involve the users of the application in the testing process, let them have a look and feel of how the new application is like.
Some errors, like bugs in the code that might cause the program not to work properly might not be easy to identify especially with a single person, and that is why it will be important if you include the users in the testing process.
The users opinion of the functionality of the application will really matter since they will be ones occasionally using it, and therefore if they do not feel like the application is not good compared to the other one, then you will need to put their views into consideration.
Regards,
Thompson Locker
It is in the nature of the program if your program is too much merged with each other so that all of its functions depend on other functions then you need to check each and all part of the program. But if your program is not associated with in some function in program then you can simply make changes to that specific portion of the program.
Such as if you want to make a change in a CLASS then you need to check only the data of class the private data is of another type while the public type is of another type. You can check your program nature in all cases and then you will be able to take a decision.
Take a brief look at your program and make sure that you have some features that are associated or not associated with each other. If some functions depend on each other then you need to check all the things.
