http://behindsoftwaretesting.blogspot.com/ TUESDAY, NOVEMBER 9, 2010 Black Box Approach: Functional testing approach focuses on application externals.

We can call it as Requirements-based or Specifications-based. Characteristics: a. b. c. d. Functionality Requirements, use, standards Correctness Business forms, Documents Does system meet business requirements

Type of Test during Black Box Approach: 1. System Testing: System test demonstrates that all programs function and work together as designed. This test is performed when all the individual component objects for a release have been integrated into a single system. Documented non-functional requirements such as performance, volume, stress, capacity and security are also verified. Particular attention is paid to regression testing during this phase. User Acceptance Testing: The testing performed for or by user is called user acceptance testing or UAT. The purpose is to ensure that end users are satisfied with the functionality and performance of the system.

2.

Techniques & Tools: a. b. c. d. e. f. g. h. i. j. k. l. m. n. o. p. q. r. s. t. Equivalence partitioning Develop program code to perform tests Boundary value analysis Develop program code to perform tests Cause-effect graphing Flow graphing tools Random testing GUI test tools Error Guessing GUI test tools Regression testing GUI / Server test tools Stress testing Load test tools Replication testing - Load test tools Data Integrity testing Data analysis tools Backup and recoverable testing Load test tools / Server test tools / GUI test tools Configuration testing Multi platform test tools Performance Testing Load test tools Functional testing Load test tools / GUI test tools / Server test tools Security testing Security test tools Operational Readiness Testing Load test tools / server / GUI tools User Acceptance testing GUI test tools Compatibility / conversion testing Load / GUI / Server test tools Benchmark Testing Benchmarking tools Usability testing Usability measurement tools Alpha / Beta testing Load / Server / GUI test tools

MONDAY, NOVEMBER 8, 2010 White Box Approach: Structural testing approach focuses on application internals. We can call it as Program-based. Characteristics: a. b. c. d. e. Module design Implementation Do modules / functions meet functional and design specifications? Do program structures meet functional and design specifications? How does the program work?

Type of Test during White Box Approach: a. Unit Testing: To verify the pieces of code against the design, to remove problems from the code, and to ensure that each component of the code executes according to functional and design specifications. Generally, developers do unit testing. Integration Testing: To verify that each software unit interfaces correctly with other software units. Developers, also testers perform integration testing.

b.

Techniques & Tools: a. b. c. d. e. f. g. h. i. j. Fault insertion Coding tools String Test GUI and Server test tools Error handling Error handling Tools Statement coverage Static and Dynamic Analyzers Decision coverage - Static and Dynamic Analyzers, Coverage analysis Tools Condition coverage - Static and Dynamic Analyzers, Coverage analysis tools Path coverage - Static and Dynamic Analyzers, Coverage analysis tools Data flow coverage Data modeling tools, Flow diagram editors Memory leak Memory usage tools Cyclomatic complexity Cyclomatic complexity Analyzers

FRIDAY, OCTOBER 29, 2010 Very Important concepts of Software Testing: Software Quality Assurance: Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'. Quality Assurance measures the quality of processes used to create a quality product. 1. It is a system of management activities. 2. It is a preventive process.

3. It applies for entire life cycle. 4. Deals with Process. It is very important for a tester to know difference between Quality Assurance and Quality Assurance. Quality control: Quality control measures the quality of a product 1.It is a specific part of the Quality Assurance procedure. 2. It is a corrective process. 3. It applies for particular product. 4. Deals with the product. Severity and priority will be assigned for a particular bug to know the importance of the bug. Severity: How severely the bug is effecting the application. Priority: Informing to the developer which bug to be fix first.

Defect: While executing the test case if u found any mismatch, the u will report it to the development team that is called defect. Bug: Once the developer accepts your defect, then it is called as a bug. Test case Test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. Test condition The condition required to test a feature.(pre condition) Test script A. Test script is the script which is generated by an automation tool while recording a application features. Test data A. Test data means the input data (valid, invalid data) giving to check the feature of an application is working correctly. Test bed Test bed means under what test environment (Hardware, software set up) the application will run smoothly. Baseline document The review and approved document is called as baseline document (i.e) Test plan,SRS(Software requirement Specification). Configuration management:

Configuration management covers the processes used to control, coordinate, and track: code, requirements, documentation, problems, change requests, designs, tools/compilers/libraries/patches, changes made to them, and who makes the changes. Verification: Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings Validation: Validation typically involves actual testing and takes place after verifications are completed. The term 'IV & V' refers to Independent Verification and Validation. Walkthrough: A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required. Inspection: An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a moderator, reader, and a recorder to take notes. The subject of the inspection is typically a document such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, not to fix anything. Attendees should prepare for this type of meeting by reading through the document; most problems will be found during this preparation. The result of the inspection meeting should be a written report. Thorough preparation for inspections is difficult, painstaking work, but is one of the most cost effective methods of ensuring quality.

http://msdn.microsoft.com/en-us/library/ff649503.aspx http://stackoverflow.com/questions/18338/software-development-life-cycle-resources http://www.softwaretestingtimes.com/2010/04/software-testing-tutorials-for.html http://puretest.blogspot.com/2009/09/testing-overview.html http://puretest.blogspot.com/2009/11/black-box-testing-refers-to-technique.html http://puretest.blogspot.com/2011/01/testing-concepts-for-beginners.html http://sql-plsql.blogspot.com/ http://www.guru99.com/software-testing.html http://www.softwaretestinggenius.com/articalDetails?qry=739 http://www.etestinghub.com/blackbox_testing.php http://www.scribd.com/doc/7951118/Manual-Testing-Material http://www.softwaretestinggenius.com/articalDetails?qry=160