Forum Discussion
yes, but only 67.0 was available.
67.0.1 became available this morning.
is there a way to see what patches you have installed from within testcomplete?
i could not find anything.
As far as I am aware, there doesn't need to be a specific TestComplete patch for every minor version of FireFox, only the major.
Is there something that's not working right with 67.0.1? Can you describe the specific situation?
Generally speaking, it's usually considered a best practice to have more direct control over your testing environments. Rather than allowing browser updates to apply automatically, I believe the recommendation is to disable automatic updates so as to make sure that a patch is available before you start using the new version.
- dbattaglia6 years agoContributor
:smileytongue:
yes, well i'm currently working on building out a functional core and not working on a 'stable' setup.
hence the auto-updated browser.
but yes, once we have some of those details settled i will ensure that the environment is stable.
in this case i was just wondering what the turn-around time is for new browser patch releases.
we are just starting work on some functional web testing at my company, so i'm learning all the stuffs.
thanks for your help tristaanogre
- dbattaglia6 years agoContributor
also, there are different patches for each major version, but the minor version tripped testcomplete, so there is sensitivity to the minor versions.
i was running 67.0 and all we well, but when 67.0.1 installed testcomplete threw an error saying i needed to look for a patch.
fyi.
Related Content
- 11 years ago
Recent Discussions
- 2 days ago