Knowledge Share

Knowledge is NOT Power IMPLEMENTATION of knowledge is Power!!!
HomePortalGalleryCalendarFAQRegisterUsergroupsLog in


 Post By Madhuri

Go down 

Posts : 142
Points : 410
Reputation : 0
Join date : 2007-12-29
Location : Chennai

Post By Madhuri Empty
PostSubject: Post By Madhuri   Post By Madhuri Icon_minitimeSat Dec 29, 2007 7:25 pm


Testing how well a system protects against unauthorized internal or external access, willful damage, etc;
This type of testing usually requires sophisticated testing techniques
It is performed to identify failures in the security system
Server configuration with an eye towards eliminating any security
Also important feature protest from hackers or virus
Ex:- Fire walls, Security socket layer, IP sec(Internet protocol security)


Testing a system under huge amounts of data or simultaneous users
The idea is system to breaking point in order to find bugs that will make that break potentially harmful
The main purpose behind this is to make sure that the system fails and recovers graceful .ex:- (Run, Wind)( Number of users)


- Buffer overflow bugs
- High volumes of data, device connections, long transaction chains
- Low memory conditions, device failures, viruses, other crises.


- Expose weaknesses that will arise in the field
- Expose security risks
- Perhaps good for assessing performance, reliability, or efficiency


- Look for functions or sub-systems of the product that may be vulnerable to failure due to challenging input or constrained resources
- Identify input or resources related to those functions or sub-systems
- Select or generate challenging data and platform configurations to test with
Ex:- large or complex data structures, high loads, long test runs,
many test cases, limited memory .etc.
- force the program to fail, watch how it fails, report the vulnerability


Testing a system to see how it recovers from errors & abnormal conditions, such as system crash, loss of device, communications or power
Ex:- Rebooted computer properly with out loss or corruption.


The process of testing an integrated hardware & software system to verify that the system meets its specified requirements
Verifies that system or subsystem perform all business functions while meeting specified performance requirements
System testing also includes the integration of modules into program,
Programs into sub-systems, and subsystems into systems
This testing is done by the development areas.
Black box type of testing that is based on overall requirements specifications; covers all combined parts of a system


Testing programs or procedures used to convert data from existing systems for use in replacement systems
When a project includes a data conversion

List of conversions

- How the converted data will be collected and verified
- How data will be compared to original data
- Compatibility of the converted data in new system
Ex:- conversion of GRAD Marks to Class Rank
- Mainframe to oracle( Missing data, correct data is tested)


Determining if software is satisfactory to an end user or customer
Usually test for main functionalities like user interface testing with cosmetic appearance of an application and required functionalities
Final stage of a software project & will often occur before the customer accepts a new system
End user are virtual users (testers)
Ex:- testing of an application by end users & and mimic the real world use
Strive for realism


- Identify failures that will arise in the hands of a person, i.e. breakdowns in the overall human/machine/software system


- Primary idea to involve users with pre-release product
- Equipment compatibility testing
- Usability evaluation
- Expert opinion/ advice
- Bug hunting
- Favourable publicity
- Increase adoption confidence of key clients
- Different objectives require different release planning/scheduling


- Design issues are more credibly exposed
- Can demonstrate that some aspects of products are incomprehensible or lead to high error rates in use
- In-house test can be monitored with flight recorders
- (capture/replay/video),debuggers, others tools

- In-house tests can focus on areas/tasks that you think are ( or should be) controversial
- Blind spots
- Coverage is not assured ( serious misses from beta test, other user tests)
- Test cases can be poorly designed, trivial, unlikely to detect sub tile errors
- Beta testing is not free, beta testers are not skilled as testers, the technical results are, mixed.
- Distinguish marketing betas from technical betas


Testing of an application when development and testing are essentially completed and final bugs and problems need to be found before the final release.
It is typically performed by end-users or others, not programmers, software engineers, or test engineers
In- house experiments using a stratified sample of target market


Testing of an application when development is nearing completion;
Minor design changes may still be made as a result of such testing
Typically done by end-users or others, not programmers or testers


Testing for ‘user-friendliness’.
Testing the ease with which users can learn and use a product
Clearly this is subjective and depends on the targeted end-user or customer
User interviews, surveys, video recording of user sessions and other
techniques can be used
Test engineers are needed, because programmers and developers are
usually not appropriate as usability testers


It is a process of confirming that all functional areas are performing
with in expectations from the time that a process begins to the point
that it reaches and “end result”
Ex:- Right from GUI interface application, web server, and database
(All components are tested for accepted results)


Testing an application under heavy loads
Some times called as volume testing or longevity testing or endurance testing
Ex:- Testing of a web site under arrange of loads to determine at what point
the systems response time degrades or fails

Depends on two main reasons

- Software reliability
- Performance testing
- Load is varied from minimum zero to maximum level of system can sustain with out running out of resources
Ex:- load, over load, high load
Testing Microsoft word by editing a very large document
Testing the printer by sending very large job
Testing the mail server with 1000 s of user mail boxes


- Expose bugs
- Memory management bugs
- Memory leaks
- Buffer over flows

Measuring load levels

- Length of session (Measured in pages)
- Duration of session (Measured in min & sec)
- Types of pages visited during the session (example:
- Home page, product information page, credit card information page )
- Typical /Most popular flow or path through website
- “%” of browse vs purchase sessions
- “%” type of users (New users or Registered users)


An initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort
Initial testing
Major functionality testing
Sanity test determines application suitability for major testing effort and connectivity among components of an application
Ex:- if the new software is crashing systems every 5minutes,bogging down systems to a crawl, or destroying databases, the software may not be in ‘sane’ enough condition to warrant further testing in its current state


Testing conducted to enable a user/customer to determine whether to accept a software product
Normally performed to validate the software meets a set of agreed acceptance criteria
Test team works with the client/customer/project manager to develop the acceptance criteria


Testing how well software performs in a particular hardware, software, operating system, or network environment


Testing that compares software weaknesses and strengths to those of competitor’s products


Testing of a full, partial, or upgrade install/uninstall process.
The installation test is conducted with the objective of demonstrating production readiness


It is continuous testing of an application as new functionality is added
requires that various aspects of an applications functionality be independent enough to work separately before all parts of the program are completed, or test drivers be developed as needed; done by programmers or by testers


Testing of individual software components
It is first level of dynamic testing and is the first responsibility of developers and then that of the test engineers
It is performed after the expected test results are met or differences are
explainable /acceptable
Typically done by the programmers and not by the testers
It requires detail knowledge of the internal program design and code


A testing phase where the tester tries to break the system by randomly trying the systems functionality


Verifying a product is accessible to the people having disabilities
(deaf, blind, mentally disabled etc)


Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm
Back to top Go down
Post By Madhuri
Back to top 
Page 1 of 1
 Similar topics
» Restraint Asphyxia - Silent Killer

Permissions in this forum:You cannot reply to topics in this forum
Knowledge Share :: Testing :: MANUAL TESTING-
Jump to: