1、MINI Edition Of Test1. Bugs, Black box Testing and White box testing（test_1,test_2）Bugs ：The term bug is often used to refer to a problem or fault in a computer. There are software bugs and hardware bugsBlack box Testing：Black Box Testing is testing without knowledge of the internal workings of the

2、item being tested. For example, when black box testing is applied to software engineering, the tester would only know the "legal" inputs and what the expected outputs should be, but not how the program actually arrives at those outputs. It is because of this that black box testing can be c

3、onsidered testing with respect to the specifications, no other knowledge of the program is necessary.Synonyms for black box testing: Behavioral, functional, opaque-box and closed-box. *Advantage for black box testing:More effective on larger units of code than glass box testingTester needs no knowle

4、dge of implementation, including specific programming languages Tester and programmer are independent of each otherTests are done from a user's point of viewWill help to expose any ambiguities or inconsistencies in the specificationsTest cases can be designed as soon as the specifications are co

5、mpile* Disadvantage for black box testing:. only a small number of possible inputs can actually be tested, to test every possible input stream would take nearly forever. without clear and concise specifications, test cases are hard to design. there may be unnecessary repetition of test inputs if the

6、 tester is not informed of test cases the programmer has already tried. may leave many program paths untested. cannot be directed toward specific segments of code which may be very complex (and therefore more error prone). most testing related research has been directed toward glass box testingWhite

7、 box Testing: White box testing strategy deals with the internal logic and structure of the code. White box testing is also called as glass, structural, open box or clear box testing. The tests written based on the white box testing strategy incorporate coverage of the code written, branches, paths,

8、 statements and internal logic of the code etc.Synonyms of white box testing: Glass, structural, open box or clear box testing. Advantage of White box testing:. As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input/data can help in testin

9、g the application effectively. The other advantage of white box testing is that it helps in optimizing the code . It helps in removing the extra lines of code, which can bring in hidden defects. Disadvantage of White box testing:. As knowledge of code and internal structure is a prerequisite, a skil

10、led tester is needed to carry out this type of testing, which increases the cost. It is nearly impossible to look into every bit of code to find out hidden errors, which may create problems, resulting in failure of the application.2. Different Test Method2.1 Whats test case?Answer: A Test Case is a

11、document which consists of some inputs and expected outputs to see whether a particular feature of an application is working correctly or not.2.2 Incremental integration testingAnswer:Continuous testing of an application as new functionality is addedRequires that various aspects of an application

12、9;s functionality be independent enough to work separately before all parts of the program are completed, or thattest drivers be developed as neededDone by programmers or by testers.2.3End-to-end testingAnswer:Similar to system testingThe 'macro' end of the test scaleInvolves testing of a co

13、mplete 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 appropriate2.4Sanity testingAnswer:Typically an initial testing effort to determine if a new so

14、ftware version is performing well enough to accept it for a major testing effort.For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a sane enough condition to warrant further testing in its curren

15、t state.2.5Regression TestingAnswer: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.2.

16、6Load testingAnswer:Testing an application under heavy loadsTesting of a web site under a range of loads to determine at what point the system's response time degrades or fails.2.7Stress testingAnswer:Term often used interchangeably with 'load' and 'performance' testing.Also used

17、 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.2.8Performance testingAnswer:Term often used interchangeably with 'stress' a

18、nd 'load' testing.Testing conducted to evaluate the compliance of a system or component with specified performance requirements. IEEE Ideally 'performance' testing is defined in requirements documentation or QA or Test Plans. s2.9Usability testingAnswer:Testing for 'user-friendli

19、ness'.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 and testers are usually not appropriate as usability testers.2.10Install/uninstall testingAnswer:Testing

20、 of full, partial, or upgrade install/uninstall processes.2.11Recovery testingAnswer:Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.2.12Security testingAnswer:Testing how well the system protects against unauthorized internal or externalaccess, wil

21、lful damage, etc;May require sophisticated testing techniques.2.13Compatibility testingAnswer:Testing how well software performs in a particular hardware/software/operating system/network/etc. environment.2.14Exploratory testingAnswer:Often taken to mean a creative, informal software test that is no

22、t based on formaltest plans or test casesTesters may be learning the software as they test it.2.15Ad-hoc testingAnswer:Conducted for very short time.Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.2.16User acce

23、ptance testingAnswer:Determining if software is satisfactory to an end-user or customer.2.17Comparison testingAnswer:Comparing software weaknesses and strengths to competing products.2.18Alpha testingAnswer:Testing of an application when development is nearing completionMinor design changes may stil

24、l be made as a result of such testing.Typically done by end-users or others,At the developers siteSome dummy data is taken2.19Beta TestingAnswer:Testing when development and testing are essentially completed and final bugs and problems need to be found before final release.Typically done by end-user

25、s or others, not by programmers or testers.At users siteSome Live data is taken2.20More On Beta TestingAnswer:At users premises, in absence of developersSome aspectsThe number of beta test sitesThe environment requiredThe support services to be providedWhether beta test software is priced or freeDef

26、ect reporting mechanismBeta testing period2.21Mutation testingAnswer:A method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detect

27、ed.Proper implementation requires large computational resources.2.22Gorilla TestingAnswer:Imagine that software developed by team is given to a Gorilla for testing.The Gorilla will randomly press some keys and it may press some keys that are acceptable inputs.2.23Field TrialAnswer:Tested on real con

28、ditions before releasing in the market.Actual working environment testing2.24Accessibility TestingAnswer:Testing carried out to ensure that the software can be used by the physically challenged persons.2.25Exhaustive TestingAnswer:Testing carried out by giving all possible inputs.Exhaustive testing

29、is very time consuming, and is impossible to do for many large projects.2.26Smoke TestingAnswer:Testing carried out to check major functionality of the software without concern forfiner details.Also referred to as quick and dirty testing.2.27Localization TestingAnswer: A product received from a soft

30、ware publisher has (supposedly) already beeninternationalized. Internationalization testing is done in order to determine how wellinternationalization has been done. E.g. will the product be easy to localize? Have all the localizable resourcesbeen separated from the source code? Does the software su

31、pport Unicode2.28 domain testingAnswer:Domain testing is the most frequently described test technique. Some authors write only about domain testing when they write about test design. The basic notion is that you take the huge space of possible tests of an individual variable and subdivide it into su

32、bsets that are (in some way) equivalent. Then you test a representative from each subset.2.29 Scenario testingAnswer:Scenario tests are realistic, credible and motivating to stakeholders, challenging for the program and easy to evaluate for the tester. They provide meaningful combinations of functio

33、ns and variables rather than the more artificial combinations you get with domain testing or combinatorial test design.2.30 Old fix regression testingAnswer:We retest several old bugs that were fixed, to see if they are back. (This is the classical notion of regression: the program has regressed to

34、a bad state.)2.31 General functional regression testingAnswer:We retest the product broadly, including areas that worked before, to see whether more recent changes have destabilized working code. (This is the typical scope of automated regression testing.)2.32 Conversion or port testingAnswer:The pr

35、ogram is ported to a new platform and a subset of the regression test suite is run to determine whether the port was successful. (Here, the main changes of interest might be in the new platform, rather than the modified old code.)2.33 Configuration testingAnswer:The program is run with a new device

36、or on a new version of the operating system or in conjunction with a new application. This is likeport testing except that the underlying code hasn't been changed-only the external components that the software under test must interact with.2.34 Volume testingAnswer:Volume testing is done against

37、 the efficiency of the application. Huge amount of data is processed through the application (which is being tested) in order to check the extreme limitations of the system3. Other Tests3.1 System testingIn this the entire software is tested. The main objective of the system Testing is to see whethe

38、r the software meets the specified requirements or not.3.2 Acceptance TestingThis is done with the realistic data of the client to see whether it has met with the requirements of the user or not. Testing here focuses on the external behavior of the project rather than the internal logic.3.3 Unit Tes

39、tingDifferent modules are tested against the specifications produced duringthe designing of the modules. Unit Testing is essentially for Verification of the code produced during the coding phase. It is done by the programmer of the module.3.4 Integration TestingIn this many module tested are combine

40、d into subsystems, which are then tested. The goal here is to determine the modules can be integrated properly. This Testing activity can be considered by testing the design.4. Important concepts in PPT test_5Static analysis involves going through the code in order to find out any possible defect in

41、 the code. Dynamic analysis involves executing the code and analyzing the output.Statement CoverageIn this type of testing the code is executed in such a manner that every statement of the application is executed at least once. It helps in assuring that all the statements execute without any side effect.5. Important concepts in PPT test_7Equivalence partitioningIn this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce