1,399 reputation
1832
bio website ballymennoniteblogger.blogspo…
location Southeastern, Pennsylvania
age 41
visits member for 3 years, 3 months
seen Feb 13 '12 at 17:46

I'm an automated and manual tester, specializing in the use of Automated QA's TestComplete testing tool for load testing and regression testing

profile for TristaanOgre on Stack Exchange, a network of free, community-driven Q&A sites


May
19
comment What is the difference between “automated testing” and “automated regression testing”?
I'm selecting this one as the answer as it does answer the question specifically. However, Ethel's answer above is a good supplement to give detailed examples of what are non-regression automated tests.
May
18
comment What are the most popular bug tracking tools?
Did a little legwork... BugCam is actually a representative of a bug reporting helper tool. This looks like a SPAM masquerading as a valid question. I've flagged it for the moderator to investigate.
May
18
comment How do I convince someone who's bought the Record-Playback line that object oriented framework is essential?
As I mentioned elsewhere, there MAY be times when record and playback is the desireable method of creating an automated test. But if the goal is to create a test that is transportable, reusable, flexible, and adaptable to different conditions, record and playback only has benefit as a research tool towards creating the other tests.
May
18
comment What are the challenges around the integration of Manual and Automated Tests?
Let me add that there are times when record and playback is suitable for certain tasks for automated testing. If your intent is to create a quick bit of code to do something and then throw it away, record and playback is DEFINITELY the way to go. But automated tests that are intended to be reused need to take a lot more thought and planning and, while record and playback may give you some simple structures to work from, it should not be the final form of your automated test.
May
18
comment What is the difference between “automated testing” and “automated regression testing”?
@Ethel started a community wiki below as an answer. Perhaps you can add these to that listing.
May
18
comment What is the difference between “automated testing” and “automated regression testing”?
@Ethel's answer below has been turned into a wiki. Perhaps you can add these answers to the wiki below.
May
18
comment What are the most popular bug tracking tools?
Agreed. Popularity and opinion, while useful for longer discussions, is a problem for SQA.
May
17
comment Testing of automated scripts
Very good points. If you're creating enough test cases to test the feature, supposedly you're actually testing your automation code as well. If the automation code reports a false negative, then you know there's something to fix. The problem as i see it is when your automation code reports a false positive (that a test passed that shouldn't have). That's when you need to actually test your code a bit to make sure that ONLY passing tests get marked as passed.
May
17
comment What benefit does having developer experience or background have on the effectiveness of a tester?
Additionally, as @Ethel points out below, the ability to help out with static white-box testing (code review) is VERY helpful to give that other pair of eyes to things
May
17
comment What benefit does having developer experience or background have on the effectiveness of a tester?
While I agree on the contamination point, I think it is helpful for a tester to know at least some of the logic that's in the code that s/he is testing in order to be able to build boundary cases and the like. Additionally, while the tester doesn't need to read the actual code to do this, having some knowledge of what happens when you don't initialize a variable, what happens when you loop on n-1 records on an array based upon 1 instead of based upon 0, etc., is helpful in, again, knowing what kinds of tests to run and how to communicate results to the developers.
May
17
comment When writing manual test cases and scripts, how much detail is too much detail when documenting the steps?
The only draw back to that is that you might still run into the problem you experienced. Most of the time, the person testing and the person writing the tests are the same person and so that person will go through on the keyboard and not find anything simply because the mouse clicks weren't run. In that case, perhaps two sets of test cases would be necessary... one for mouse, one for keyboard.
May
16
comment reporting cumulative test results
That kind of is how I felt reading that, Joe. There's no visibility and reliability of the reporting of the next version if tests that passed previous versions are already marked as passed in the next version.
May
16
comment reporting cumulative test results
Could you retitle this so that it reads more as a question? Also, this seems to be less of a question and more of a gathering of "Anyone else run into this? What's your experience?"
May
16
comment In TestComplete 8, what tasks are best suited for keyword tests and which ones are best suited for “hand coded” scripts?
I'm rather surprised. Is TestComplete not that standard of a tool? Or is the feature so new that no one else has any answers to share?
May
16
comment How do you adapt agile testing techniques to a regulated industry?
What kinds of documents do you generate, then? You make a good point, but it seems, at least in my experience with Agile (which, to be honest, was NOT very well implemented IMO), the design, development, and even testing processes were VERY light on any formal documentation. There was no formal design spec, test plan, or documented test cases, just the User Stories and the brief task descriptions on the KanBan for Developer, Documentation, and Testing tasks. This might just be a very BAD implementation of Agile but its what I have to go on at this time.
May
16
comment How do I convince someone who's bought the Record-Playback line that object oriented framework is essential?
That answer is well worth the 50 rep bounty... I can't think of any better way to answer it than to bring in such an expert that gives good, practical, insider look as to what record and playback was designed to do. Thanks, @Justin
May
16
comment How do you adapt agile testing techniques to a regulated industry?
That seems to be the problem, though, at least within the company that I'm working. Perhaps it's just my perception but it seems that, when it comes to regulated industries, the idea of less documentation and less formalized design seems to go counter to what auditors of such regulated industries require. They want to know exactly what you did, how you did it, why you did what you did, etc., in order to make sure everything is within necessary compliance
May
13
comment When writing manual test cases and scripts, how much detail is too much detail when documenting the steps?
Now THAT'S a fantastic answer and, with the image, it gives all the information needed without a lot of extra verbage. Thanks, Justin, that's exactly what I needed.
May
13
comment Techniques to write good acceptance criteria for user stories
I've found that, when using this methodology of softare development and design, the user story is definitely the key. Get a good handle on that, and everything just falls into place. If the user story is too general, you end up getting bogged down and dragging out development. If it's too specific, then you get bogged down in a lot of little detailed stories. Finding that balance is key.
May
13
comment When writing manual test cases and scripts, how much detail is too much detail when documenting the steps?
Agreed. There's all the data that is setup behind the scenes, configuration requirements, environment requirements, etc. That stuff needs to be documented as well. I guess it's the stuff like "Click on the OK button" as specific step to be executed after a step for entering data on a form rather than just including in the step for data entry "Enter and save data XYZ in the form". That's a trivial example but that's kind of what I'm aiming at in this question.