771 reputation
16
bio website
location San Antonio, TX
age
visits member for 1 year, 9 months
seen Sep 14 at 2:41

Automated software test tool junkie (currently TestComplete, Jira, Atlassian but expanding) on primarily Java apps to enhance exploratory testing.


Jul
23
comment What mathematical skills does testing require?
Rsf - I absolutely agree that a basic understanding of statistics is necessary for testing, but for a different reason. The improper use of statistics can quickly lead to the use or trust in misleading or harmful test metrics. Arming testers with that knowledge can help improve their analytical skills.
Jul
2
comment Where to get started with UFT?
For general information, check out Albert Gareevs site: automation-beyond.com Otherwise, I should warn you that GUI automation is not for the faint of heart and is generally not successful. BTW, Selenium is an open source UFT tool for web pages.
Jun
10
comment Recording data during tests execution
This is very probably the actual reason for this requirement. However, this approach could actually increase lawsuits. Specifying documentation of a specific result would require it be tied to a specific test case. That approach tends to inhibit exploratory testing, which could uncover many additional flaws that users will eventually find. Whether those static test cases exhibit "due diligence" would be something lawyers would love to argue over.
Jun
9
comment Recording data during tests execution
Absolutely not! Again, the question was why someone would require that level of documentation (i.e. the thought process behind it). I have had teams that were working on very critical processes that did require that level of documentation, but that was long ago. Personally, I think it is a complete waste of time. It is better to characterized "how" the tests are performed instead of detailed results (unless there is a bug). BTW, I have seen that level of detail a few years back using the QTP GUI automation tool. It was never of much use to me.
Jun
6
comment Recording data during tests execution
True, you can always rerun the test. However, you did specify that this is for (I assume) FDA certification. Let's say you ran the test and it passed. One year later, you find that the software failed in the field and the failure is traced to that test scenario. You set up the system to rerun the test and ... the test fails. That is the reason for the documentation. This is not a case of CYA, but a necessary step for tracing root cause of the problem.
Jun
4
comment validations for text fields like country, State, cities
If this is a true text field, then there is an abundance of test approaches on the web that you can research. Remember that you are trying to show it is broken, so how it reacts to invalid data (including special characters) is definitely something to explore.
Jun
4
comment What does QA support for production push/release
Are you looking for general comments or do you have a specific team structure in mind (e.g. agile or scrum)? Specifics always help in this forum. :)
Jun
2
comment Proper pattern for setting up tests of basic database operations
Kate - Your last sentence is interesting. One question would be whether it is more useful to test the actual scenarios in the application and take "before" and "after" snapshots of the resulting data. Getting into the atomic operations may be more of a unit test in the dev environment.
May
27
comment What is the purpose of expected results for individual test case steps?
@prockel: I whole-heartedly agree. Now script that test case into a tool and assign single expected result. Getting back to the original point, the context of the test case you are running is what should drive the expected result, not the scripted text. That is one reason that overly scripting test cases is many times (not always) counter productive.
May
25
comment What is the purpose of expected results for individual test case steps?
dzieciou - I think you are making my point. Taking existing bugs into account while testing is one of many layered oracles to be considered. The point is that any metric associated with tests can be (and often is) taken out of context - deciding which is the "better" one is not productive (IMHO), except within the context of a specific team for a specific application under test. Lucas asked "why" the tool worked that way, I gave him the best reason I could think of then gave him some potential pitfalls with using it. Note: It may actually still be useful in his context. ;)
May
19
comment Are test set cases always meant to be run in succession?
Hmm ... we seem to be getting buried on terminology. By "full succession". I assume you mean a test that is intended to run straight through without stopping for failures (as opposed to the "fail-closed" model that Kate mentioned). Without digging through the code to capture the dependencies, I would recommend you do some heavy manual exploring and build a model of the dependencies. On one application, I kept a hierarchical list of dependencies in a Word document in outline mode. I ended up with a document a few hundred pages long. Understanding is key before automation.
May
5
comment What are anti-patterns in test automation?
If you are using the automation as a means of test setup rather than a tripwire test, then keyboard automation provides an alternative to mouse click automation if that method is unreliable.
May
5
comment What are anti-patterns in test automation?
An exception that produces a stack trace display at the GUI can be leveraged to create a SQL injection attack if the control codes are not intercepted properly in text field.
May
4
comment What are anti-patterns in test automation?
An example of intermittent operation is applications that throw exceptions. That is a security issue in itself, but some teams will allow exceptions to be thrown during development that are very tough to anticipate using automation. Another intermittent case would be race conditions, such that a stimulus may infrequently require a screen refresh for the correct answer to appear. That is sometimes left as a "low" defect because users are not confused by it.
May
4
comment What are anti-patterns in test automation?
For accessibility, the standards require that you provide a "accessible name" or "accessible text" ("alt text" in web apps) information that is passed to the external reader. Every tool I have used has leveraged that information if it exist. Another related requirement is keyboard accessibility. Having keyboard operation as an alternative to mouse clicks is a wonderful alternative automation method for GUIs that change their visual layout.
May
4
comment Testing a tester with example projects
Be sure to find a handful of sites/applications/examples and randomize them. If you only use one, word may get around and you may find the "aptitude" of your applicants increasing dramatically over time. ;o)
Apr
16
comment What's a significant slogan for the formal review process?
If this is found to be inappropriate for this forum, you can also try submitting it as a discussion at www.softwaretestingclub.com. A lot of creative, twisted minds running around there. :)
Apr
15
comment Which automation tool can be used to automate a desktop application whose frontend is developed on MS Access
I did a quick web search and found a hit at the SmartBear TestComplete user forum, where someone asked about testing an ADP file app. You may want to submit your specific question there. Hope that helps!
Mar
31
comment How to solve miscommunication issues with qa in order to decrease task redundancy?
Procedures are simply agreements between members of a team. If you are not acting as a team (no communication), then procedures can't help. The only way this will work is if all of the members of the team are convinced that sending potential bugs to the testers for verification is faster than sending them to the developers to fix immediately. That requires trust and communication. Without that, you will have to ask what is the actual role of the testers in the organization? I feel for you - I've been on projects like that in the past and it wasn't pretty. Good luck!
Mar
24
comment QA Testing Process
The topic of automated script maintenance is important. When the script breaks, you have pressure to quickly get it working again, but you need to understand whether the failure is caused by an intended change. Naturally, that requires the automation be maintained "real time". The person running the scripts should be both an experienced tester and an experienced script writer to be efficient - a tough combo to find.