test management

Articles

Two golden retrievers lying on the floor, photo by Gulyás Bianka The Who, What, When, and How of Pair Testing

Pair testing can help you speed up your test assignment and provide more quality to your test results. But who can do pair testing, and when should they do it? And what kind of pair testing is best for your situation? This article gives you more information about how you should conduct pair testing in order to maximize its benefits.

Simon Schrijver's picture Simon Schrijver
Which Testing Tool has more demand and growth in IT Industries?

There are so many tools for marketing that are pitted against each other, but each tool has got some special feature associated with it specifically. Such as

 

•For Automation testing, Selenium and UFT(QTP) are preferred

•For Performance  testing, JMeter and LoadRunner are preferred

•For Services testing SOAP UI are preferred

•For unit testing mbunit, testing is preferred

 

However, Selenium and OATS (Oracle Application Testing Suite) are getting increasingly popular among the testers for the testing purposes.

 

Selenium-

 

Jack Ramon's picture Jack Ramon
Simulators/Emulators vs Real devices: Which one do enterprises prefer?
james lees's picture james lees
testing Adopt an Innovative Quality Approach to Testing

How much testing is really enough? Given resources, budget, and time, the goal of comprehensive testing seems impossible to achieve. It’s time to rethink your test strategy and start innovating.

Rajini  Padmanaban's picture Rajini Padmanaban
High Level Test Plan/ Test Scenarios for Telecom Based Applications- OSS and BSS

New to Telecom Domain- Need sample Test Plan or Test Scenarios or some document to kick start Telecom Based applications.

 

IF this is not specific, I would like to receive whatever documents available to begin telecom based testing.

Subramanian A
Setting up / test management tool & automation tool

Hi,

 

just started in new company as sw tester / (sw test manager). Before they did not have a dedicated tester there so I am the first one and only one now.

There are about ~10 sw developer in team. 

Product have HW that connects to Cloud server and there is web page where to control / see data it send. I should do manual testing and verify that data it send is correct (via web page)

There is a testplan in Excel and those cases are now run manually. I really thing some cases are must to automate (like loging, create some data, delete some data, and testing same with different browsers)

TestReport is now created by entering issues to this Excel sheet.

Redmine is in use(as issue tracking? I have not used that before: only worked with TFS & QC)

 

Now my job as a tester/test manager role is to make this QA process work better.

As company is not very big I am looking not-expensive solutions.

Pete Best's picture Pete Best
Alon Eizenman Testing with the Lights On: An Interview with Alon Eizenman
Video

In this interview, Alon Eizenman, the CTO and cofounder at SeaLights Technologies, discusses his many experiences with startup companies, how software teams are adapting to the current demand for speed, and why you need data before you take testing actions.

Jennifer Bonine's picture Jennifer Bonine
Automation’s Role in the Fall of Software Testing

Has the rise in test automation resulted in product releases of lesser quality? Besides adopting more comprehensive automated scripting, there are process and organizational dynamics to consider.

John Tyson's picture John Tyson
Identical bugs under a magnifying glass When Testers Should Consider a Bug a Duplicate

When can a bug report be considered redundant because it is already reported in the bug management system? If you ask the developers, if two bugs are caused by the same mistake in the code, it’s enough to report one of them. But Michael Stahl has good arguments from a tester's perspective about why it's better to err on the side of over-reporting bugs.

Michael Stahl's picture Michael Stahl
Path breaking away from a road Learn More from Tests That Stray off the Happy Path

Unit tests exercise various paths through your codebase. Some are happy paths where everything you expect goes right. These tests are boring. The interesting tests are the ones where your code goes hurtling off the happy path. The trick is to capture the diversity of a multitude of unhappy paths without needlessly duplicating unit tests. Here's how you can improve the quality of your unit testing and fix it more effectively.

Steve Poling's picture Steve Poling

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.