Sunday, June 30, 2013
Explain the single and two level directory structures
Posted by
Sunflower
at
6/30/2013 12:30:00 PM
0
comments
Labels: Characters, device, Directory, File system, files, Individual, Limitations, Location, Logical, Operating System, Physical, Single-level, Standard, String, Structure, System, Two-level, Users
![]() | Subscribe by Email |
|
Friday, February 4, 2011
User Interface Testing - Interface testing strategy
The user interface model is reviewed to ensure that it conforms to customer requirements and to other elements of analysis model. During testing, focus is shifted towards application specific aspects of user interaction as they are manifested by interface syntax and semantics.
The goal of interface testing is to:
- uncover errors related to specific interface mechanism.
- uncover errors in the way interface implements semantics of navigation, web application functionality or content display.
Objectives that should be achieved are:
- Interface features are tested to ensure that design rules, aesthetics, and related visual content are available for user without error.
- Individual interface mechanisms are tested in a manner that is analogous to unit testing.
- Each interface mechanism is tested within the context of a use case or navigation semantic units for a specific user category.
- The complete interface is tested against selected use cases and navigation semantic units to uncover errors in the semantics of the interface.
- The interface is tested within a variety of environments to ensure that it will be compatible.
Usability testing evaluates the degree to which users can interact effectively with the web application and the degree to which the web application guides user actions, provides meaningful feedback, and enforces a consistent interaction approach. Usability tests are designed by a web engineering team, but the tests themselves are conducted by end users.
Steps to be followed are :
- define a set of usability testing categories and identify goals for each.
- design tests that will enable each goal to be evaluated.
Posted by
Sunflower
at
2/04/2011 03:24:00 PM
0
comments
Labels: Applications, Content, Design, Goals, Individual, Interfaces, Mechanisms, Objectives, Semantics, Software testing, Strategy, Syntax, User Interface, Users
![]() | Subscribe by Email |
|
Wednesday, November 17, 2010
Understanding Scenario Based Testing
Scenario based tests (SBT) are best suited when you need to tests need to concentrate on the functionality of the application than anything else.
Suppose, you are testing an application which is quite old and it is a banking application. This application has been built based on the requirements of the organization for various banking purposes. Now, this application will have continuous upgrades in the working.
Let us assume that the application is undergoing only functional changes and not the user interface changes. The test cases should be updated for every release. Over a period of time, maintaining the test ware becomes a major set back. The Scenario based tests would help you there.
As per the requirements, the base functionality is stable and there are no user interface changes. There are only changes with respect to the business functionality. As per the requirements and the situation, it is clearly understood that only regression tests need to be run continuously as a part of testing phase. Over a period of time, the individual test cases would become difficult to manage. This is the situation where we use scenarios for testing.
To derive scenarios, the following can be used as a basis:
- From the requirements, list out all the functionality of the application.
- Using a graph notation, draw depictions of various transactions which pass through various functionality of the application.
- Convert these depictions into scenarios.
- Run the scenarios when performing the testing.
Scenario based tests are not only for legacy application testing, but for any application which requires you to concentrate more on the functional requirements. I f you can plan out a perfect test strategy, then the scenario based tests can be used for any application testing for any requirements. Scenario based tests will be a good choice with a combination of various test types and techniques when you are testing projects which adopt UML (Unified Modeling Language) based development strategies.
Posted by
Sunflower
at
11/17/2010 12:38:00 PM
0
comments
Labels: Application, Functional, Individual, Quality, Requirements, Scenario based testing, Scenarios, Software, Software testing, Stable, Test cases, Tests
![]() | Subscribe by Email |
|