soccerjo
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Who does your Automated Testing? QA or Development?
Great discussion! I'm in my first QA job, coming from my first development job. Here, we have dedicated QAs doing (almost) all of our test automation, but that is probably first and foremost due to time constraints. We have an automation backlog already, and we also have very optimistic goals for our developers. I do think someone doing test automation benefits immensely from development/scripting experience, but shouldn't be a normal feature developer, as the different perspective is important.5KViews0likes0CommentsRe: TestComplete 11.31 and Chrome 58
I wanted to add that the issue here seems to be that Chrome automatically updated from 32-bit to 64-bit, which is very odd. Uninstalling and re-installing the 32-bit version seems to fix the problem. I'm surprised the 64-bit version doesn't work with TestComplete, but I realize that I should be using a newer version of TC by now.1.7KViews0likes3CommentsTestComplete 11.31 and Chrome 58
I've been using TestComplete 11.31.2420.7 with Chrome, and during the day today my Chrome seems to have updated to 58.0.3029.96 (Official Build) (64-bit). I believe the version I had previously (that did work) was 58.0.3029.81 (Official Build) (32-bit). I do not know how Chrome automatically updated to 64-bit. Now all objects found are offset from the actual objects in the browser. Using the object spy, the outlines I see are not where they should be. When TC finds an object and tries to click it, it clicks far away from where the object actually appears. Has anyone else seen this? Does anyone know what versions of Chrome TC 11.3* actually supports? Any tips/suggestions? I've been able to roll by vm back to the "before" version of Chrome listed above, but this is only a short-term solution.1.8KViews0likes4CommentsRe: Test Complete getting crashed
I often see this error when I am using debugging to step through a test, and I try to perform an action on an object that does not actually exist. When I am not debugging, the test just throws the standard log error. You may want to check that all of your objects exist when you expect them to.1.8KViews1like1CommentRe: DevOps
Figured I'd throw my 2 cents in here. My husband has a devops role, but at his company, this simply means he is knowledgeable about both operations (servers, networking, sysadmin stuff) and development. He works between those 2 teams, helping coordinate, avoid blame wars, and get problems fixed that need a multi-team approach. Devops doesn't really relate to testing, from what I can tell. It is the new "in" term, though, and as such probably means different things to different people. I feel like the intent was to have people who had skills in 2 areas, who could tackle problems that related to both areas with a more well-rounded perspective.3.8KViews2likes2Comments