Posts Tagged ‘look & feel testing’

The Future of Testing: Testers as Designers

Thursday, September 9th, 2010

the-future-of-testing-testers-as-designersModern testers play largely a role of late cycle heroics that often goes unappreciated come review and bonus time. When we find the big bug it is because we were supposed to … that’s the expectation. When we miss the big bug, people ask questions. It’s often a case of ignored-if-you-do and damned-if-you-don’t.

This is going to change and it is going to change soon because it must.

As testing and test techniques move earlier in the process testers will do work more similar to software design than software verification. We will place more emphasis on designing quality strategy for all software artifacts and not just the binary. We will spend more time recognizing the need for testing rather than actually executing test cases. We will oversee and measure automation rather than building and debugging it. We will spend more time reviewing the status of pre-existing tests than building new ones. We will become designers and our work will be performed at a higher level of abstraction and earlier in the lifecycle.
(more…)

Web Testing: A Next-Day Service

Tuesday, July 28th, 2009

Softheme offers web testing as one of our next-day services. What does this mean? This means that we have our own testing environment installed onsite (working machines, testing systems, etc) and test engineers ready to start at any time. We also provide an access to the defect-tracking system fully set up and ready for work on our side. These conditions let us start working on your project immediately and noticeably accelerate the testing process. Practically, we can start testing a project the next day after a customer’s final decision.

Usually we suggest the following engagement models for web testing projects:

1. Full-cycle testing

Basing on the requirements provided by a customer we develop a test strategy, test plan, test cases (functional, performance, usability, look and feel, and others), and then start with the first iteration of testing. At this point the team executes all required types of testing specified in the test strategy and reports discovered defects to the defect-tracking system on a daily basis. After the first iteration of testing is completed, the team starts regression testing and works in conjunction with the development team – all encountered and fixed defects are retested; all tests are re-run to ensure the functionality works as expected after bug-fixing.

(more…)

SWIT Investor Day