What are the principles of system testing in management information system?

5. It includes uniqueness, standardization and universality, expansibility and stability, easy identification and memory, short and unified format and easy modification.

6. A test case is a set of test inputs, execution conditions and expected results compiled for a specific goal to test the program path or verify whether it meets specific requirements.

At present, there is no classic definition of test cases. Generally speaking, it refers to the description of a specific software product testing task, which embodies the testing scheme, method, technology and strategy. The contents include test objectives, test environment, input data, test steps, expected results, test scripts, etc. , and form a document.

Different types of software have different test cases. Different from systems, tools, control and game software, the user requirements of management software are more inconsistent and change more quickly. The author is mainly engaged in the testing of enterprise management software. Therefore, our method is to separate test data and test scripts from test cases. Test cases are often test schemes designed for the functions, business rules and business processing of software products. The test of each specific function or operation path of the software constitutes a test case.

With the development of software industry in China, software testing is also developing. From the initial part-time testing of software programmers to the establishment of independent full-time testing departments in software companies. Testing has also developed from simple testing to formal testing, including: preparing test plans, writing test cases, preparing test data, writing test scripts, implementing tests, testing evaluation and so on. The testing method has developed from simple manual testing to both manual and automatic testing, and there is a trend to the third-party professional testing company.

To make the end users satisfied with the software, the most powerful measure is to clarify the expectations of the end users, so as to verify these expectations and confirm their effectiveness. Test cases reflect the requirements that need to be verified. However, verifying these requirements may be realized by different testers in different ways. For example, executing software to verify its function and performance can be realized by a tester using automatic test technology; The shutdown step of the computer system can be completed by manual testing and observation; However, market share and sales data (and product demand) can only be achieved by evaluating products and competitive sales data.

Because it may not be possible (or necessary) to verify all requirements, whether the most suitable or critical requirements can be selected for testing is related to the success or failure of the project. Choosing the requirements to be verified will be the result of weighing the cost, risk and the necessity of verifying the requirements.