@agrawalravi90 I agree that we have too many pbs_issue.py files/test suites and it is difficult to find the test suites that I might want to run to exercise a code change. But on the other hand, I can understand why it is happening…when I add a feature I want to have all of my tests in one place so it’s easy to run all of my new tests.
To help me understand your proposal, let’s use an example:
I am adding a new feature, as part of my feature qsub and qstat will also be changed. My feature is something that changes the default behavior of qsub and qstat (i.e. no specialized situation).
Would your proposal mean that I would have to add tests to pbs_qsub.py and pbs_qstat.py in addition to pbs_myfeature.py?
If so, that would make running the tests to test my feature more difficult since tests are spread across multiple files. In the future, fixes to the feature would also mean the next developer will not know which tests to run to fully test the feature.
If not, that would mean anyone who runs pbs_qsub.py will not test my features changes to qsub. This would be status quo today.
Who decides which option fits the situation? If it is left up to us, many of us will choose the simplest path (1 new file) and we’re right back where we are.