Test basis 5

One 、CS and BS Software architecture

CS The client side - Server architecture and BS Browser - Server architecture , Sum up the difference  ：
 efficiency ：c/s Efficient , Some content is already installed in the system ,b/s Load the latest data every time 
 upgrade ：b/s Seamless upgrade ;c/s Delete the old version and install the new version  
 Security ：c/s More secure , Need to install 、 register 、 Sign in ;b/s You can use it with a browser , Low level of safety  
 Development costs ：b/s The cost is low ;c/s Different systems need different developers , The high cost 

Two 、 History of language development

1、 machine language 、 Machine code （0 and 1）： The bottom of the computer can recognize 
2、 assembly language ： The language closest to machine code , Still obscure , It runs faster than other high-level languages 
3、 High-level language ：c、php、java、python...

3、 ... and 、 Software test classification

1. By method ：
 Black box 
 White box 
 Gray box 

2. By direction ：
 function 
 performance ： The benchmark 、 load 、 pressure 、 Concurrent 
 Security 

3. By stages ：
 unit ： Code block 、 function 、 class 
 Integrate ： Interface 
 System ： function 、 performance 、 stability 、 Security 、 Ease of use 、 compatible 、web、app,UI、 Portability 
 check before acceptance ：α Internal measurement of the company ,β User beta 

4. By object ：
web
app
 The Internet of things 
 vehicle 
 The embedded 
 big data 
AI
 Applet 

5. Divide by code ：
 static state 
 dynamic 

6. Other types ：
 smoking 
 Return to 
 Explore 

Four 、 By stage

1、 Unit testing is also called module testing ; Test the smallest program module ;
2、 Integration testing is also called assembly testing , Usually on the basis of unit testing , Individual modules are tested together 
3、 The system test , It refers to testing the whole software system as a whole 
4、 The acceptance test ：
(1)α test ：Alpha  It's an in-house version , Usually only within the software developers , Or among loyal fans , This version of the software bug More , It's better for ordinary users not to install 
(2)β test ：Beta It's a public beta version , It's a beta version open to all users , Free release , Because there will be some bug The existence of 
(3)γ test ：Gamma Version is the candidate version of the official version 

5、 ... and 、 Whether to view the source code

1、 Black box testing ： Focus on business logic , Between input and output 
2、 White box testing ： To study the source code and program structure 
3、 Grey box testing ： The state between black and white 

6、 ... and 、 Sort by whether to run

1、 The static test ：  It refers to not actually running the tested software , It's just checking the program code statically 、 Possible error process in interface or document . 
2、 Dynamic testing ：  It refers to the actual operation of the program under test , Input the corresponding test data , The process of checking whether the actual output matches the expected result .

7、 ... and 、 According to whether it is automated

1、 Manual testing ： Also called manual testing , The test that the tester carries out manually  
2、 automated testing ： Use code or tools to help manual testing 

8、 ... and 、 The test strategy

1、 Smoke testing ： Smoke test is to test the most basic functions of the system , Ensure that the basic functions and processes can go through  
2、 regression testing ： When repairing a BUG after , Test the previous test case again under the new code 
3、 Random test ： Random testing is mainly to retest some important functions of the tested software , It also includes testing the parts that are not covered by the current test cases  
4、 Exploratory testing ： Exploratory testing means designing and executing tests at the same time . Testers learn the tested system through testing .

Nine 、 defects

 Software defect ： It refers to various problems and errors in software or programs ; It will cause the software products to fail to meet the needs of users to some extent 

Ten 、 Criteria for determining software defects

1.  The software does not meet the functions indicated in the requirements specification  
2.  The software has requirements specifications that indicate where errors will not occur  
3.  The function of the software is beyond the scope specified in the requirement specification 
4.  The software does not meet the goal that the requirements specification does not specify but should achieve  
5.  Software testers think software is hard to understand , Not easy to use , Slow running speed , Or the end user experience is bad .（ Poor experience ）

11、 ... and 、 The cause of software defect

 Software defects are inevitable , The causes of software defects are summarized as follows ： 
1. Demand interpretation 、 Wrong record or definition  （ Wrong understanding of requirements ）
2. The design documentation states that there are errors or spelling errors  （ System design error ）
3. Code description 、 Program code error  （ Coding errors ）
4. There is an error in the hardware or software system 

Twelve 、 Types of software defects

 Function error  
 Interface error  
 Compatibility flaws  
 Ease of use issues  
 Suggestions for improvement 

 In fact, there is another classification ：
 Suggestive questions 
 General defects 
 Serious defects 
 Fatal defect 

13、 ... and 、 Testing principle

1、 It can only prove that there is a problem with the software , It cannot be proved that there is no problem （ Testing can only find software errors , It doesn't prove that the software is error free ）
2、 It cannot be exhausted （ Exhausting ） test , It should be classified and tested 
3、 The testing work should be involved as soon as possible , Reduce repair costs 
4、 The defects are clustered , This principle ：20% There is... In the module of 80% The defects of 
5、 Test dependent environment （ System 、 browser ）
6、 Pesticide phenomenon （ A tester tests a system , A long time , The number of defects found is reduced , Defects are rarely found . terms of settlement ： Introduce new test cases , Testers exchange testing work , Form complementary thinking ）
7、 There is no defect fallacy （ Even if the software does not find defects , As long as it does not meet customer needs , This is not high-quality software ）

fourteen 、 Definition of software testing

 Manual and automated means to test , Objective to find the difference between the expected results and the actual results 

15、 ... and 、 The purpose of software testing

 With the least manpower 、 material resources 、 financial , Find problems in the software and fix , To reduce business risk 

sixteen 、 The test case

 Definition ： Is a set of test inputs designed for a specific purpose 、 Documentation of execution conditions and expected results . What to measure ？（ Test purpose ） How to measure ？（ The test strategy ）

seventeen 、js Basic grammar

ctrl+？  Comment shortcut key 
alert Pop-up dialog box , The content in parentheses can achieve the effect of prompt text , It must be placed in English 、 In double quotes , It is not recommended to omit the last semicolon ,
	 example ：
	alert();
	alert(' Your phone bill is insufficient   Please recharge in time ');
	alert(" Your network fee is insufficient ");
 Writing position ：script The label is written in html The last position of the code , Other js The program should be written in this pair of labels 

eighteen 、 Event Syntax

<script type="text/javascript">
	 Rule of grammar ：
 Event source . Event type =function(){
		 The command to execute when the event occurs 
}
	
	//document  Represents the scope of search in the whole document 
	// document.getElementById('bz')     
	 Event source ：    adopt id The value of is bz The button 
	 The following short code  document.getElementById('bz')   On the browser f12, Find the second console, Copy in and press enter to run , See if you can find the corresponding label 
// onclick   Represents the type of event （ Click the left mouse button ）
// function(){  Commands to execute  }

// example ：
	documen.getElementById('xw').onclick=function(){
		alert('test');
	}


	//getElementsByClassName('testclass')    look for class by testclass The label of 
	//onclick    It must be lowercase ！！
	// [ Numbers ]    On behalf of the number one , from 0 Start recording numbers （ Index value ）
	document.getElementsByClassName('testclass')[0].onclick=function(){
		alert('testclass');
	}

//onmouseover   Mouse move in event 
//onmouseout   Mouse out event 
document.getElementsByClassName('testclass')[1].onmouserover=function(){
		alert(' Mouse move in event ');
	}
odcument.getElementsByClassName('testclass')[2].onmouseout=function(){
		alert(' Mouse out event ');
	}

</script>

<!DOCTYPE html>
<html>
	<head>
		<meta charset="UTF-8">
		<title></title>
	</head>
	<body>
		<input type="button" value="test" id="test"/>
		<input type="button" value="testClass1" class="class" />
		<input type="button" value="testClass2" class="class" />
		<input type="button" value="testClass3" class="class" />
	</body>
</html>

<script type="text/javascript"> alert("this is demo"); document.getElementById("test").onclick=function(){
       alert("thank for you click!"); } document.getElementsByClassName("class")[0].onclick=function(){
       alert("this is getElementsByClassName Test"); } document.getElementsByClassName("class")[1].onmouseover=function(){
       alert("mouse over"); } document.getElementsByClassName("class")[2].onmouseout=function(){
       alert("mouse out"); } </script>

nineteen 、Js Three uses of ：

Js Embedded ：js The script is written in <head> In the label , Or in <body> After label 
Js Outside the chain ：js The script is placed in an external file 
Js inline ： take js Written in html On the label , But it is not recommended. , No code separation , It's inconvenient to modify 

twenty 、 operation html Elements

<!DOCTYPE html>
<html>
	<head>
		<meta charset="UTF-8">
		<title></title>
	</head>
	<body>
		<p id="test1">this is test</p>
	</body>
	<script type="text/javascript"> document.getElementById("test1").innerHTML="update innerHTML content" </script>
</html>

The 21st 、JS Variable ：

 Variable naming conventions ：
 Variable names should consist of letters 、 Numbers 、 Underline 、$ constitute , Chinese is not recommended  
 Variable name cannot start with a number  
 Variable names are case sensitive （y  and  Y  It's a different variable ）

<!DOCTYPE html>
<html>
	<head>
		<meta charset="UTF-8">
		<title></title>
	</head>
	<body>
		<p id="test1">this is test content</p>
	</body>
	<script type="text/javascript"> var content="update content" document.getElementById("test1").innerHTML=content; </script>
</html>

Twenty-two 、JS Functions and events ：

JS Function syntax ：
 use function Keyword to define  
 Put the code block in braces  
 By using   Function name ()  To call a function   When a function is called , Will execute code within the function 

<!DOCTYPE html>
<html>
	<head>
		<meta charset="UTF-8">
		<title></title>
	</head>
	<body>
		<p id="test1">this is test</p>
	</body>
	<script type="text/javascript"> function update(){
       document.getElementById("test1").innerHTML="update innerHTML"; } update(); </script>
</html>

23 、JS event ：

onchange：HTML  Element change  
onclick： The user clicks  HTML  Elements  
onmouseover ： Users in a HTML Move mouse over element  
onmouseout：  User from a HTML Element up mouse off  
onkeydown：  User presses keyboard key  
onload ： Browser finished loading page 

<!DOCTYPE html>
<html>
	<head>
		<meta charset="UTF-8">
		<title></title>
	</head>
	<body>
		<h1>js</h1>
		<p id="demo"> Here is the time </p>
		<input type="button" name="" id="btn1" value="now date？" />
		<br />
		<input type="text" name="" id="" value="" placeholder="please input username：" onchange="changeUsername()"/>
	</body>
	<script type="text/javascript"> function changeUsername(){
       alert("username update"); } document.getElementById("btn1").onclick=function(){
       document.getElementById("demo").innerHTML=Date(); } </script>
</html>