What are the functional testing methods?

Question 1: What are the software testing methods 1? According to whether to check the internal structure of the program, it is divided into:

(1) black box test: only care about the input and output results.

(2) White-box testing: study the source code and program structure.

2, according to whether to run the program is divided into:

(1) Static testing: refers to the process of statically checking possible errors in program codes, interfaces or documents without actually running the software under test.

Static tests include:

For code testing, it is mainly to test whether the code meets the corresponding standards and specifications.

For interface testing, it is mainly to test whether the actual interface of the software meets the description in the requirements.

For document testing, it is mainly to test whether the user manual and requirement description really meet the actual needs of users.

(5) Dynamic testing refers to the process of actually running the tested program, inputting the corresponding test data and checking whether the output results are consistent with the expected results.

3, according to the stage:

(1) unit testing refers to checking and verifying the smallest testable unit in the software.

Stud module refers to the module called by the simulated module under test, and driver module refers to the superior module of the simulated module under test. The driving module is used to receive the test data, start the tested module and output the results.

(2) Integration testing is the next stage of unit testing, which means assembling the unit modules that have passed the test into a system or subsystem, and then testing, focusing on testing the interface departments of different modules.

The integration test is used to check whether each unit module can work together and run normally.

(3) System testing refers to testing the whole software system as a whole, including testing the function, performance and software and hardware environment in which the software runs.

The main basis of system testing is the document system requirements specification.

(4) acceptance testing refers to the test that is mainly conducted by users or participated by quality assurance personnel such as testers in the later stage of system testing, and it is also the last working procedure for software to be formally delivered to users.

Acceptance testing is divided into A testing and beta testing, in which A testing refers to internal testing involving users, testers and developers, and beta testing refers to public testing after internal testing, that is, it is completely handed over to end users for testing.

4, black box test is divided into functional test and performance test:

1) function testing is an aspect of black-box testing, which checks whether the functions of the actual software meet the needs of users.

Include logic function testing.

Ui test ui = user interface

Usability testing: it refers to checking the software system from the perspective of rationality and convenience of software use, so as to find out the inconvenience caused to users in the software.

Compatibility test: including hardware compatibility test and software compatibility test.

2) Performance test

The performance of software mainly includes time performance and space performance.

Time performance: mainly refers to the response time of specific software transactions.

Spatial performance: mainly refers to the system resources consumed when the software runs.

Software performance testing is divided into:

General performance test: refers to the performance test that allows the tested system to run in normal software and hardware environment without any pressure.

Stability test, also known as reliability test, refers to the continuous operation of the tested system to check the stability of the system during operation.

Load test: refers to the continuous operation of the tested system within the pressure limit it can withstand to test the stability of the system.

Stress test: refers to continuously increasing the pressure of the tested system until the tested system collapses, so as to test the maximum pressure that the system can bear. (Verification system or ...>& gt

Question 2: In software testing technology, what methods are used for functional testing? Common methods of functional testing.

( 1)

Check the page links to see if each link has a corresponding interface.

(2)

Correlation check, delete

/

Will adding one project affect other projects? If yes, is it correct?

(3)

Check whether the button function is correct.

(4)

Check the length of the string and enter something that exceeds the required specified string length.

See if the system checks,

Yes or no

An error has occurred.

(5)

Character type check

(6)

Punctuation check

(7)

Chinese character processing, garbled or wrong.

(8)

Check the integrity of the information brought out,

Look at the information and

update

information age

,

Check whether all the information you have filled in is with you.

appear

,

Whether the information brought out is consistent with the information added.

(9)

Duplicate information. In some information with unique names, enter duplicate names or

Proof of identity

, to see if the system has

Processing, duplicate names include whether it is case-sensitive, input spaces before and after input, and see if the system processes it.

( 10)

Check the delete function. In some places where multiple items can be deleted, click the Delete button without selecting anything to see how the system handles it.

( 1 1)

What should I do when I choose one or more?

( 12)

Check whether the addition and modification are consistent,

Check whether the requirements for adding and modifying information are consistent.

,

For example, add necessary items.

,

It should also need to be revised.

;

Adds an item specified as an integer.

,

Modification must also be an integer.

.

( 13)

Check and modify duplicate names. When modifying, change the items that can't be repeated into the existing contents to see if the error will be handled. At the same time,

See if you can report the mistake of renaming yourself.

( 14)

Submit the form repeatedly, a record that has been submitted successfully,

hardworking

After submission, see if the system handles it.

( 15)

Check multiprocessing

hardworking

Critical situation

(16) search

cheque

：

Zaiyou

search

The function of the input system exists and does not exist,

See if the result is correct;

( 17)

If you can enter more than one

search

Conditions,

At the same time, reasonable and unreasonable conditions can be added,

See if the system handles it.

Correct.

( 18)

The location of the input information, and the location of the cursor when the information is input.

( 19)

Check whether uploading and downloading files are realized, whether the uploaded files can be opened and uploaded.

The format, whether the system has explanation information.

(20)

Check the required items and whether there is any prompt information for the required items.

(2 1)

Shortcut key check, whether to support common shortcut key check.

(22)

Check the Enter key. Press Enter directly after input to see how the system handles it and whether it will report an error.

Question 3: What are the personnel, resources, progress, test objectives, test scope and test completion standards? Is it included in the test plan?

Question 4: What tools are commonly used in software testing? There are many kinds of testing tools, mainly the following:

Test management tools: MQC, TestManager and QACenter, among which defect tracking: change management tools can also be used.

Functional test automation: QTP, RFP, QARun, Silk

Performance testing tools: Loadrunner, Robot, QAload, WAS, Silk Performance.

Unit and white box testing tools: Junit, Jmeter, devpartner, skeleton probe, Purify Plus.

Security test: Appscan, Fortify

Question 5: How to test the software? What kinds are there? The first test method is to try to verify whether the software is "working". The so-called "working" means that the functions of the software are executed in a pre-designed way. The second test method is to try to prove that the software "doesn't work".

There are also two categories: white box method and black box method.

White box method: when you know the process of the program, test the code of your program with different data to verify the correctness of the program, including conditional test, path test and conditional combination. . . .

White box method is used in the early stage of program development.

Black box method: it is mainly used in the later stage of program development, that is, after the process test of the program is correct, the results of the program are tested. What are the causal methods, marginal value methods, etc.

Specifically, you can buy a book on software engineering.

There is another way:

Functional testing, acceptability testing, user interface testing, exploratory or open testing, performance testing, regression testing, violence testing, integration and compatibility testing, assembly/installation/configuration testing, internationalization support testing and localization language testing;

Some attacks are test methods.

Question 6: What are the objectives and standards of software testing? What are the test methods? What are the test steps? Specifically, testing should generally achieve the following objectives:

1. Ensure that the product has achieved the promised or announced functions, and all the functions accessible by users have clear written descriptions-in a sense, it is the same idea as ISO900 1.

The lack of clear written documents is a short-term behavior of the manufacturer and an irresponsible performance. The so-called short-term behavior refers to the lack of clear written documents, which is not conducive to the smooth delivery of products, easy to conflict with users, and affect the reputation of manufacturers and future cooperation with users; At the same time, it is not conducive to the later maintenance of products, and it also makes manufacturers spend too much user training and technical support costs. From the long-term interests, this is not cost-effective. There are few software products that leaders have been exposed to, such as big products and thin documents.

Of course, for the rapid prototyping (RAD) development projects, the writing and maintenance of written documents are the most important, the most difficult and the most easily overlooked.

Finally, the imperfection or even inaccuracy of written documents is also the biggest and most troublesome problem encountered in the testing work. Its direct consequences are low test efficiency, unclear test objectives and insufficient test scope, which leads to the failure to give full play to the role of the final test and unsatisfactory test results.

2. Ensure that the products meet the requirements of performance and efficiency.

A product with low operating efficiency (low performance), unfriendly user interface and inconvenient user operation (low efficiency) cannot be said to be a competitive product.

What users are most concerned about is not how advanced and powerful your technology is, but how much benefit he can get from these technologies and functions. In other words, the user cares about how much he can get out of it, not how much you put in.

3. Ensure that the product is robust and can adapt to the user environment.

Robustness, that is, stability, is the basic requirement of product quality, especially for business-critical or time-critical working environments.

In addition, it is impossible to assume the user's environment (except for some projects). For example, many newspaper users have low configurations and use them at the same time with some third-party products.

The principle of testing-good enough

For relatively complex products or systems, zero bug is an ideal, and good enough is our principle.

The principle of good enough is a principle to measure the input/output ratio: it is irresponsible to test insufficiently; Over-testing is a waste of resources and an irresponsible performance. The difficulty of our operation lies in: how to define what kind of testing is insufficient and what kind of testing is excessive. At present, the only available answer is to formulate the minimum passing standard and content of the exam, and then analyze the specific problems. The most obvious example is the product testing of China FIT3.0.

Test Law-Konikin's Law and 80-20 Principle

1, koninkin's law.

In the production of software products, it is the concept of total quality management (TQM). The key factors of product quality are analysis, design and realization, and testing should be an auxiliary means of inspection. Other management, support and even cultural factors will also affect the quality of the final product. It should be said that testing is the necessary condition and the most direct and quickest means to improve product quality, but it is by no means the fundamental means. On the other hand, if all the weights to improve product quality are put on testing, it will be a terrible and long disaster.

2. The 80-20 principle of bugs.

Generally speaking, 80% of bugs can be found and avoided in the review and testing work in the analysis, design and implementation stages, and the remaining 80% of bugs can be found in the system testing. The last 5% bugs may only be exposed after users have widely used them for a long time. Because testing can only ensure that as many errors as possible can be found, but not all errors can be found.

Methods of software testing:

1, which is divided into:

(1) black box test: only care about the input and output results.

(2) White-box testing: study the source code and program structure.

2, according to whether to run the program is divided into:

(1) Static test: it means that the software under test is not actually run, but only run statically ... >; & gt

Question 7: What tests does the functional test include? What test method is used? Five points. It depends on the relevant national standards and product standards.

Because it is a functional test, if the above standards are not available, the inspection department will proceed from the user's standpoint and combine with the instruction manual.

Question 8: What are the commonly used test methods or means of chip function? This is a program, an executable code, engaged in activities, disrupting the normal use of computers, making computers unable to use normally or even damaging the entire operating system or computer hard disk. Just like biological viruses, computer viruses have unique replication capabilities. Computer viruses spread rapidly and are usually difficult to eradicate. They can put their own documents. When files are copied or transferred from one user to another, they spread. This program does not exist independently, it is hidden in the executable program, whether destructive or not, but it is also contagious and potential. Lighter will affect the running speed of the machine. The machine is not running, but the machine is paralyzed, which will bring immeasurable losses to users. This destructive influence is usually placed on computer virus programs.

In addition to replication, some computer viruses have some similar characteristics: a new polluting program can spread virus vectors. When you see that virus carriers seem to stay in text and images, they may also destroy files, reformat your hard disk or cause other types of disasters. If the virus is parasitic on a contaminated program, it will still bring you trouble through the occupied storage space and reduce the performance of your computer.

?

Computer viruses have the following characteristics:

Parasitism of (1)

In other schemes, when the program is executed, the destructive effect of the virus is not easy to be found before the program is started.

(2) Infection

Computer virus is not only destructive and harmful, but also contagious. Once a virus is replicated or mutated, it is difficult to stop its speed.

(3) Diving

Some viruses, such as time bombs, have a pre-designed attack time. Black Friday virus, for example, realized this within a predetermined time, and suddenly broke out when conditions were ripe, destroying the system.

(4) concealment

Some hidden computer viruses are detected by virus software, some are not detected at all, and some are fickle when hidden, which are usually difficult to deal with.

?

When a computer is infected, it will show different symptoms. The following are some common phenomena for users' reference.

(1) The machine cannot be started normally.

After the power is turned on, the machine cannot be started or can be started, but it takes longer than the original starting time. Sometimes suddenly the screen goes blank.

(2) the running speed is reduced

If you find that when you run a program to read data for longer than before, the number of saved files or file transfer files increases, which may be caused by a virus.

(3) Fast disk space is smaller.

Memory resident's virus programs can reproduce, so the memory space is even "0", and no user information is obtained.

(4) Changes in file content and length

For the file on the disk, its length and content will not change, but due to the interference of virus, the length of the file may change the content of the file, and garbled code may appear. Sometimes the contents of a file can't be displayed or displayed, and then it disappears.

(5) Frequent "crash" phenomenon

Normal work will not lead to death, even for beginners, command input will not collapse. If the machine often crashes, it may be because the system is infected.

(6) External equipment can't work normally.

If there is a virus in the machine, there may be some abnormal situations in the work of the external equipment because of the control system of the external equipment, which can not be explained theoretically and empirically.

The above list is only some common virus manifestations, and some other special phenomena are bound to be encountered, which require users to judge for themselves.

?

First of all, we should think seriously, strengthen management and prevent the invasion of viruses. Scan all external floppy disk replicators for floppy disk viruses. If so, the virus must be deleted so that you can infect your computer with the virus. In addition, because the virus is potential, it may cover up some old viruses and will attack when the time is ripe, so it is often checked on the disk and killed in time if found. On the basis of thinking about the importance, the technical support of effective virus scanning and antivirus methods is adopted. There are usually two ways to check and remove viruses, one is to add an anti-virus card to the computer, and the other is to use anti-virus software with basically the same working principle and more anti-virus software for ordinary users. Remember, preventing and eliminating viruses is a long-term task, not once and for all.

Under what circumstances will a computer virus appear? ......& gt& gt

Question 9: What are the methods of integration testing? In these cases, there are many implementation schemes for integration testing, such as bottom-up integration testing, top-down integration testing, big bang integration testing, sandwich integration testing, core integration testing, layered integration testing and usage-based integration testing. For specific related questions, you can go to sogou to test WeChat official account and ask ~

Question 10: What are the test methods and their advantages and disadvantages? 1, resume testing

Recovery test mainly checks the fault tolerance of the system. When there is a problem with the system, can you correct the error and restart the system within the specified time interval? The recovery test should first use various methods to force the system to fail, and then verify whether the system can recover as soon as possible. For automatic recovery, it is necessary to verify the correctness of reinitialization, checkpoint (Mechani * * * s), data recovery and restart. For the artificial intervention repair system, it is necessary to estimate the average repair time to determine whether it is within the acceptable range.

2. Safety test

Security testing checks the ability of the system to prevent illegal intrusion. In security testing, testers pretend to be illegal intruders and try to break through the defense line through various methods. For example, ① trying to intercept or decipher passwords; (2) Customize the protection mechanism of the software destruction system; (3) Deliberately causing system failure and attempting to illegally enter during recovery; (4) Trying to infer the required information by browsing non-confidential data, and so on. Theoretically, as long as there is enough time and resources, there is no inaccessible system. Therefore, the criterion of system security design is to make the cost of illegal intrusion exceed the value of protected information. At this point, illegal intruders are unprofitable.

3. Strength test

The strength test checks the program's resistance to abnormal conditions. Strength testing always forces the system to run under abnormal resource configuration. For example: ① When the normal interrupt frequency is one or two per second, run a test case that generates ten interrupts per second; (2) Quantitatively increase the data input rate and check the reflection ability of input sub-functions; (3) Run test cases that require the largest storage space (or other resources); (4) Running test cases may cause the virtual memory operating system to crash or the disk data to shake violently.

4. Characteristic test

For those real-time and embedded systems, even if the software part meets the functional requirements, it may not meet the performance requirements. Although each test step includes the performance test from the unit test, only after the system is truly integrated can the performance be fully and reliably tested and run in the real environment. The purpose of performance testing is to accomplish this task. Performance testing is sometimes combined with strength testing, which usually requires the support of other software and hardware.