:: QC Boss :: Testing, Independent Software Testing, Manual Testing, Website Testing, Functionality Testing, Usability Testing, QC, QA, UAT

Archive for May 2009

STOP

without comments

As a website owner, you would ideally wish to convert maximum number of visitors to your site into customers. Imagine a customer leaving your shop without buying anything just because your salesman/ agent could not explain the product to him, even though you had what the customer wanted. The consequence of an incompatible browser is exactly the same. You may have a wonderfully designed site for your business, but what if its features are working only in Internet Explorer and not in Firefox, Netscape or Safari? You would straightaway lose your potential customers.

 

Sometime back, not many browsers were around to choose from in order to browse the Internet. But today, there are several browsers apart from the different versions in each of them. This scenario leads to a lot of browser compatibility issues in your website, which are seldom noticed by the developers. It needs a very systematic and professional testing approach to find these bugs and resolve them.

 

Though there are many sources available both online and offline which give suggestions and short-cuts to achieve cross browser compatibility, the best way to ensure browser compatibility is to test all the pages of your website against the different browsers and their versions. We at QC Boss have an expert team to provide you with the excellent services including Browser Compatibility Testing to test your website against all such issues.

Written by QCBoss

May 11, 2009 at 8:44 am

A Strategic Approach to Software Testing in Real-Time Systems

without comments

Testing is a group of activities that can be designed in beforehand and executed systematically. With this reason a set of stages that we can place particular tests case design techniques and test approaches should be developed for the software engineering procedure. A set of testing strategies have been developed, which gives a template for testing and all include the following features:

1. Testing starts at the modular level and works outward towards the integration of the complete system.

2. Diverse testing techniques are appropriate at diverse points in time.

3. Testing is performed by the programmer of the software and an independent test group.

4. Testing and debugging ate diverse activities, but debugging must be included in any testing strategy.

Testing the Real-Time Systems:

A strategy for testing in real-time systems must include low-level tests that are required to verify that a small source code segment has been executed correctly as well as high-level tests that that validate main system functions based on client requirements. The special characteristic of real-time systems makes them a main challenge when come to testing. The time-dependent type of real-time applications adds a new difficult element to testing.

Not only do the programmer have to look at black/white box testing but also the timing of the data and the parallelism of the projects. In many situation testing data for real-time system may raise errors when the system is in one state but to in others.

Comprehensive test cases design methods for real-time systems have not evolved yet. However, the 4-stage approach can be put as:

1. Task Testing is the first stage is to test independently the tasks of the real-time software.

2. Behavioural Testing using system models produced with CASE tools the behaviour of the real-time system and examine its actions as a result of external events.

3. Intertask Testing is done once errors in individual tasks and in system behaviour have been observed testing passes to time-related external events.

4. Systems Testing; software and hardware are integrated and a full set of systems tests are introduced to uncover errors at the software and hardware interface.

Written by QCBoss

May 8, 2009 at 8:05 am