I think that you are looking in the wrong direction for testing scripts.
Yes, it is possible that your code will work on Intel, but not on AMD, or in Windows Vista Home, but not in Windows Vista Professional. But if you do not do something very closely related to low-level programming in the first case or to the details of the OS implementation in the second, the chances are small. You could say that itβs never scary to experience every conceivable scenario. But in real life there should be a certain limit of resources available to you for testing. Testing on different processors or different OS in most cases does not test your program, it tests the compiler, OS or processor. How much time do you have to check other people's work? I think your time will be better spent testing more scripts in your own code. You do not give details about what your application does, but just to take one of my own examples, it would be much more productive to conduct a daily test for selling products that our own company produces in comparison with products that we resell from other manufacturers, or testing sales tax rules for different conditions or something else.
In practice, I rarely test deployment on Windows and deployment on Linux, not to mention different versions of Windows, and I rarely burn on it.
If I were to write low-level device drivers or some, this would be a different story. But ordinary applications? Do not waste your time.
source share