Manual testing is still the most popular method of software application testing and to make it efficient we at OsB always start with careful planning of the test process and test cases. Our specialists use mainly the V model described in BS7925 Standard for Software Component Testing promoted by British Computer Society to test the application through it's entier development lifecycle.

We offer you the services of a team of professsional software testers who work according to newest international standards and methodologies. We are performing all types of tests from document testing to System Test or User Acceptance Test

Is a framework to describe the software development life cycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.

The most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code.

testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc.

black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.

determining if software is satisfactory to an end-user or customer.

testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers are usually not appropriate as usability testers

similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort.

re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.

term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans

term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.