Testing Testing 1,2,3
-
I've got a BIG hammer. Does that count?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
I've got a BIG hammer. Does that count?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Thor, are you going to do some unit tests with frost giants again?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." -
That depends. Can you lift it up? :laugh:
Your time will come, if you let it be right.
-
Thor, are you going to do some unit tests with frost giants again?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada."Not until they get the bugs out of Ragnarök V2.0
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Not until they get the bugs out of Ragnarök V2.0
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
It already must be a bug if Thor survived Ragnarök 1.0
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." -
Testing is often a part of the IDE an/or the operating system. So developer can also do a good job on testing.
Press F1 for help or google it. Greetings from Germany
-
_Maxxx_ wrote:
(i.e. not a dev) but is keen and smart.
Testers must be destructive.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." -
Our lovely Tester is looking into automated testing; She knows little about it, is not particularly technical (i.e. not a dev) but is keen and smart. I have literally no experience of any testing tools, so I am hoping you lovely chaps will be able to recommend some you may have used, and give me a bit of an overview of what makes 'em good (or bad!) :)
PooperPig - Coming Soon
Testing is for sissies. Which might unfortunately apply literaly, given the description you provided.
-
Our lovely Tester is looking into automated testing; She knows little about it, is not particularly technical (i.e. not a dev) but is keen and smart. I have literally no experience of any testing tools, so I am hoping you lovely chaps will be able to recommend some you may have used, and give me a bit of an overview of what makes 'em good (or bad!) :)
PooperPig - Coming Soon
i have years of experience in test automation (even developed a test tool for ui automation myself) and i can tell you, that test automation is essentially software development. you develop software (sometimes with the help of powerful libs) to automate other software. most of the tools provide some capture replay functionality but to be honest capture replay does not work well. its like programming spagetti code ;) what you will want is dev know-how to write scripts/tests in a programming language. i can recommend ranorex as a very versatile tool with a very nice c# api.
-
i have years of experience in test automation (even developed a test tool for ui automation myself) and i can tell you, that test automation is essentially software development. you develop software (sometimes with the help of powerful libs) to automate other software. most of the tools provide some capture replay functionality but to be honest capture replay does not work well. its like programming spagetti code ;) what you will want is dev know-how to write scripts/tests in a programming language. i can recommend ranorex as a very versatile tool with a very nice c# api.
Thanks; I figured there's got to be some level of coding - even if it is 'only' some scripting. I hadn't heard of ranorex - I just gave the web page a quick squiz and it does look interesting... I may have to give our tester some programming lessons !
PooperPig - Coming Soon
-
Thanks; I figured there's got to be some level of coding - even if it is 'only' some scripting. I hadn't heard of ranorex - I just gave the web page a quick squiz and it does look interesting... I may have to give our tester some programming lessons !
PooperPig - Coming Soon
well i think if you want to be productive in test automation you will quickly see recurring patterns emerge that you will want to encapsulate to increase productivity. well thats where programmings starts :) you will want to look into concepts like PageObjects to reduce the impacts changes have.
-
Our lovely Tester is looking into automated testing; She knows little about it, is not particularly technical (i.e. not a dev) but is keen and smart. I have literally no experience of any testing tools, so I am hoping you lovely chaps will be able to recommend some you may have used, and give me a bit of an overview of what makes 'em good (or bad!) :)
PooperPig - Coming Soon
-
Our lovely Tester is looking into automated testing; She knows little about it, is not particularly technical (i.e. not a dev) but is keen and smart. I have literally no experience of any testing tools, so I am hoping you lovely chaps will be able to recommend some you may have used, and give me a bit of an overview of what makes 'em good (or bad!) :)
PooperPig - Coming Soon
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
Our lovely Tester is looking into automated testing; She knows little about it, is not particularly technical (i.e. not a dev) but is keen and smart. I have literally no experience of any testing tools, so I am hoping you lovely chaps will be able to recommend some you may have used, and give me a bit of an overview of what makes 'em good (or bad!) :)
PooperPig - Coming Soon
_Maxxx_ wrote:
Our lovely Tester is looking into automated testing
First is to determine what the exact interface(s) is to be tested and how. If you want to test an IE browser client on windows 7 it is substantially different than testing a GUI application on win 95-win 10 and max OSX and still again different if you want to do security testing on a Rest API. Of course presumably you already use a unit testing framework yourself.
_Maxxx_ wrote:
She knows little about it, is not particularly technical
In my experience non trivial testing of non-trivial applications is going to require 'programming' in some sense of the word. Not in the languages that you are familiar with but in rather in terms of the testing tools. Complex tests or complex applications could also require supplementary tools written (probably by a developer) to supplement testing. One complex case can be creating and managing versions of test data and loading that data into a database to allow version testing with a database.
-
_Maxxx_ wrote:
(i.e. not a dev) but is keen and smart.
Testers must be destructive.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada."CDP1802 wrote:
Testers must be destructive.
True that, but it's your fault if they succeed at it. It's no good telling them(me) to not push the red button, that's like catnip. (This test is still failing. So, I'm doing my job, what are you doing?) Also, who would you prefer finding that little flaw that opens up your entire accounting system, a tester or a black hat? Assuming (s)he doesn't turn to the dark side.
-
i have years of experience in test automation (even developed a test tool for ui automation myself) and i can tell you, that test automation is essentially software development. you develop software (sometimes with the help of powerful libs) to automate other software. most of the tools provide some capture replay functionality but to be honest capture replay does not work well. its like programming spagetti code ;) what you will want is dev know-how to write scripts/tests in a programming language. i can recommend ranorex as a very versatile tool with a very nice c# api.
werinus wrote:
i can recommend ranorex as a very versatile tool with a very nice c# api.
Can't argue with that, but it has its quirks too. I used it for 2 months a year+ ago, it nicely records physical actions so you can build tests without coding, but then breaks for no apparent reason, so you have to dive into the code. I never got conversant with it enough to say I know it well.
