Ankit Gupta
Week - 12
Software Technical Reviews   

A review process can be defined as a critical evaluation of an object. It includes techniques such as walkthroughs. The objective of the reviews is to search out design weaknesses, faulty designs, or designs which may be cost drivers. Problems can often be identified early from the data item submissions, and attempts can be made to clarify these problems on a case-by-case basis before the review to avoid major problems and surprises at the meetings. Program includes a functioning requirement Research and Development. Technical reviews would be basic to monitor growth. Program includes a functioning requirement but no Research and Development. The system is mostly commercial off the shelf gear. It could include some non-developmental items and limited trainer unique equipment like brackets or cabinets to mount the COTS equipment or maybe some panels built to simulate to body of weapon. Limited technical reviews held in conjunction with scheduled progress reviews would be necessary. Program includes a performance specification  but no Research and Development. The system is all commercial off the shelf equipment. It could include some non-developmental items but no trainer unique equipment. If the software were complex, then limited technical reviews held in conjunction with scheduled progress reviews would be necessary. If the software is not complex, then only progress reviews might be necessary. Program includes a functioning requirement and no Research and Development. The Government is mostly concerned with schedule in this case as implementation is already determined and the contract type will be fixed price. Scheduled progress reviews would be all that is basic.

Ankit Gupta
Week - 11

What is the good test case

Test case help us to discover the information. different types of tests cases are more effective for different classes of information. Tests case can be good in a variety of way.  No test case will be good in all of them. People tend to create test cases according to certain testing styles, such as domain testing or risk-based testing. Good domain tests are different from good risk-based tests. In my view, a test case is a question that you ask of the program. The point of running the test is to gain information, for example whether the program will pass or fail the test. It may or may not be specified in great procedural detail, as long as it is clear what is the idea of the test and how to apply that idea to some specific aspect feature, for example of the product. If the documentation is an essential aspect of a test case, in your vocabulary, please substitute the term “test idea” for “test case” in everything that follows. Find safe scenarios for use of the product find ways to get it to work, in spite of the bugs. Sometimes, all that you’re looking for is one way to do a task that will consistently work--one set of instructions that someone else can follow that will reliably deliver the benefit they are supposed to lead to. 

• 
  

Ankit Gupta
Week - 10

Functional testing focus on what the system does, rather than how does it work.  Non functional testing is focus on what systen does and how it does. Both function are focus on behavior.  white box tests function system based on how does the system work from inside.
functional test bases on funtional requirements. Funtional tests are different than integration tests. A functional integration test will focus on the functionality of a collection of interfacing modules, usually in terms of the partial or complete user workflows, use cases, operations, or features these modules provide.A functional system test will focus on the functionality of the application as a whole, complete user workflows, use cases, operations, and features. A functional system integration test will focus on end-to-end functionality that spans the entire set of integrated systems.

Ankit Gupta
Week -9
Integration Testing

In this phase of testing, individual modules are combined and teste as a group. Data trasfer between the modules is tested thoroughly. Integration testing is carried out by tester.
Big-Bang

• Wait for all modules to be developed.
• Time consuming
• Difficult to trace root cause of bugs.

other approach are, would be functional increment & sandwich - which is combination of top to down and bottom to up. The choice of approach chosen depends on the system architecture and location of high rish modules.
Once all the individual units are created and tested we can start doing the integrated testing.

Studs

• Used in top down approach
• top most modules is tested first 
• dummy program of lower level components

Driver

• Used in bottom up approach
• lowest modules are tested first
• dummy program for higher level component

Ankit Gupta
Week-8
Software Testing Life Cycle

Contary to poular belief, software testing is not a just a single activity. it consists of series of activities carried out methodologically to help certify your software product. These activities constitute the software testing life cycle.
Requirent Analysis - during this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may interact with various stakeholders to understand the requirements in detail.
Activities- identify types of tests to be performed.
grater details about testing priorities and focus.
Test Planning- This phase is also called test strategy phase typically, in this stage, a senior QA manager will determine effort and cost estimates for the project and would prepare and finalize the test plan.
Test Case Development- this phase involves creation, verification and rework of test cases & test scripts. test data, is identified / created and is reviewed and then reworked as well.
Test Environment setup- Test environment decides the software and hardware conditions under which a work product is tested. test environment setup is one of the critical aspect of testing process and can be done in parallel with test case development stage test team may not be involved in this activity if the customer team provides the test environment in which case the test team is required to do a readliness check of the given environment.