table of Contents
4. The correctness of the data:
Report test:
Page test, function test, report authority test, data correctness test, report performance test
1. Page test:
Interface inspection: 1. The overall page is beautiful and uniform; 2. Input box: length, mandatory input, input format, etc.;
Report format :
1, reporting the correctness of the field represented , integrity , font, size, aesthetic appearance , requires reduction or wrapped data is too long;
3. Whether the overall style of the report meets the regulations or the format , alignment, border, interval, etc. set by the user
4. Paging: When the output content is too much, whether the paging is correct. Whether the page turning function is correct
5. Friendliness: Whether the data or graphs are clear, and the display of the data conforms to the user's habits; whether the data that needs special reminder (such as totals, abnormal data) is highlighted; whether there are comments in complex algorithms, where users do not understand or are easily confused;
6. The format of the data: whether the decimal place, thousands sign, rounding, etc. are consistent with the report settings; whether the unit or tax rate conversion is correct;
7. Data sorting: whether the sorting method is consistent with the report setting (if there is no setting, is there a clear default sorting method, such as alphabetical or numeric sorting)
Preview and printing of reports :
1. The display integrity in the preview;
2. In the case of multiple pages, the header of page 2 is displayed;
3. Whether the specific printing situation required by the demand can be realized; (for example, the printing uses the specified template)
4. Print after preview;
5. Print directly without preview
6. Requirements for testing various printers;
7, report export : format to CSV, Excel, pdf and so on .
2. Function test:
1. The query function is normal; 2. Enter each condition combination query; 3. Data query range test
3. Permission test:
1. The condition definition of the report: In the condition selection area, some drop-down boxes should not be able to display data outside the scope of user authority. For example, when ordinary clerks use reports, the report name drop-down box cannot display reports that can only be viewed by managers. When some input text boxes are divided into levels, it is necessary to test the corresponding input of data beyond the authority.
2. Report content: The content in the report cannot display data that the user does not have permission to view.
Fourth, the correct data of:
General report test: The report of themainbusiness system, the report is to provide help for the business.
1. The correctness of the statistical data of the report : the source of the data: which table, which field it comes from, the correspondence between the value in the database and the interface data .
2, reports, statistics data integrity : the amount of data in the database is consistent, consistency details and total and so on .
3. Whether the data processed by the system is consistent with the result of manual calculation .
Big Data BI reports: Afterdataextraction,cleansing,conversion, and thenshowup in the report.
From the perspective of cost savings in the entire project, the layer-by-layer test effect is the best. The complete revision rate is also the highest.
First establish a test data model, simulate all application tables, establish simple and easy-to-track data use cases, test the underlying data tables, and compare the data through SQL statements and manual calculations. It is more flexible to test the accuracy of report data in the system,
① Compare the overlapping reports in the system .
② Compare the summary of sub-reports with the parent report, that is, compare the summary of monthly reports with annual reports, and compare the summary of daily reports with monthly reports. This is only one aspect, which can be considered from the dimensional relationship, region, administrative level, time, and individual Start with other parties and conduct summary comparisons .
③ Use SQL and manual calculation for comparison.
To the next is error-prone situation :
● Wrong use of the original table: Because there are many tables, and there is no unified data relationship corresponding table, it is easy to use the table wrong.
● Data processing logic error: This is easy to cause disputes due to the deviation of the tester and the developer's understanding of the requirements, so in the requirements review, the data processing rules are clearly expressed in expressions or pseudo-code. There are also programmer errors, deviations in logic programming, improper handling of boundary values and special circumstances.
● Data permissions: Different users have different viewing permissions for data. This is related to data security.
● Data error: the reserved digits of the data, whether the data is processed and calculated is the last calculation using digits reserved and rounding.
● Data errors caused by data errors in the dictionary table, for example, according to gender statistics, purchase volume, men and women in the table are reversed, or gender missing items are not considered, and if else is used, this is the missing item in the table Is counted as the else condition. Or the user state should be considered in the logic, and fields with similar data states are easy to be ignored, and the test should be considered.
● The last item, when the amount of data is quite large, statistics should consider the cutting speed, that is, the completeness of the data. Due to the lag of data cutting, the data is incomplete and the statistical results are incomplete. For example, the statistics of yesterday’s sales, but yesterday’s data did not completely go from the business system data to the data pool, and the data at the end of the month, due to the incomplete data cut on the last day, resulting in inaccurate statistics in the first month.
5. Report performance test:
1. Check the response time of the report interface and the time when the data is loaded through the packet capture tool.
2. Test the specific response time of SQL through the interface test function.
3. Test the execution time of SQL through the database execution plan.