An automated testing method for a margin management software

Abstract

The application belongs to the field of software testing, and particularly relates to a kind of automatic test method of margin management software. The automatic test method of margin management software of the application adopts different test cases to automatically generate scripts to generate test case sets, reduces the repetitive work of testers, and avoids human errors introduced by testers due to too many test data. The test process is divided into first monitoring voting test and second monitoring voting test. On the basis of not changing the software architecture, complete testing of requirements is realized, and the intermediate link of fault state testing is simplified, which facilitates fault injection. Through automatic comparison of test results, automatic comparison of test case set results of a large number of signals can be realized at the same time, which saves test time and facilitates fault positioning. Test case records in conformity with formats can also be generated as attachments of test reports.

Description

Technical Field

[0001] The present invention relates to the field of software testing, and in particular to an automated testing method for redundancy management software. Background Art

[0002] Redundancy management software, a key component of the aircraft management system, is responsible for monitoring the working status of redundant information, identifying and isolating faults, integrating detected fault information, and reporting them, thereby ensuring the effective coordination of redundant channels. Therefore, the security of redundancy management software directly impacts aircraft flight safety and the functionality of other systems.

[0003] Redundancy management software features a large number of signals and a high level of functional integration, resulting in a significant amount of repetitive work during testing, making it suitable for automated testing. Currently, testing of redundancy management software primarily involves testers inputting pre-designed test cases one by one and observing the consistency between the voting results and the test cases, resulting in low testing efficiency. Traditional testing methods involve numerous test cases, are time-consuming, and have high testing costs. Fault injection involves numerous fault states, making the operation confusing, and various factors influence each other, making some requirements unavailable. Furthermore, this method relies heavily on testers themselves, making it easy to introduce test case errors and increasing the difficulty of troubleshooting.

[0004] Therefore, it is desired to have a technical solution to overcome or at least alleviate at least one of the above-mentioned deficiencies of the prior art. Summary of the Invention

[0005] The purpose of this application is to provide an automated testing method for redundancy management software to solve at least one problem existing in the prior art.

[0006] The technical solution of this application is:

[0007] An automated testing method for redundancy management software, comprising:

[0008] Step 1: According to the interface volume of the requirement specification, classify the input signal into different signal types according to the signal source and intermediate state differences;

[0009] Step 2: For input signals of different signal types, write an automated test case generation script based on the input signal value range, signal fault type, and state fault type to generate the first monitoring and voting test case set for each input signal;

[0010] Step 3: Import the first monitoring and voting test case set into the simulation running environment to drive the redundancy management software to run;

[0011] Step 4: Set the test run time. After the test is completed, use the test result automatic comparison script to compare the results of the first monitoring voting test;

[0012] Step 5: Using the output signal of the first monitoring and voting as the input signal of the second monitoring and voting, and dividing the input signal of the second monitoring and voting into different signal types;

[0013] Step 6: For input signals of different signal types, write an automated test case generation script based on the input signal value range, signal fault type, and state fault type to generate a second monitoring and voting test case set for each input signal;

[0014] Step 7: Import the second monitoring and voting test case set into the simulation running environment to drive the redundancy management software to run;

[0015] Step 8: Set the test running time. After the test is completed, compare the second monitoring voting test results through the test result automatic comparison script to generate a test report.

[0016] In at least one embodiment of the present application, in step 1, according to the interface volume of the requirement specification, the input signal is divided into different signal types according to the differences in signal sources and intermediate states, including:

[0017] According to the interface volume of the requirement specification, the input signals are divided into electromechanical signals, flight control signals, and avionics signals according to the signal source;

[0018] According to the differences in intermediate states, the input signals from various signal sources are divided into: analog signals, discrete signals, and enumeration signals.

[0019] In at least one embodiment of the present application, electromechanical signals are divided into: analog signals and enumeration signals according to differences in intermediate states.

[0020] In at least one embodiment of the present application, the flight control signal is divided into: analog signal according to the difference in intermediate states.

[0021] In at least one embodiment of the present application, avionics signals are divided into: analog signals, discrete signals, and enumeration signals according to differences in intermediate states.

[0022] In at least one embodiment of the present application, in step 2, when the input signal is an analog signal of an electromechanical signal, the input signal includes:

[0023] Device status, serdes bus status, CCDL bus status, heartbeat word status, valid bit status, and transition status.

[0024] In at least one embodiment of the present application, in step 2, when the input signal is an enumeration signal of an electromechanical signal, the input signal includes:

[0025] Device status, serdes bus status, CCDL bus status, heartbeat word status, and transition status.

[0026] In at least one embodiment of the present application, in step 2, when the input signal is an analog signal of a flight control signal, the input signal includes:

[0027] Device status, serdes bus status, mode word status, valid bit status.

[0028] In at least one embodiment of the present application, in step 2, when the input signal is an analog signal of an avionics signal, the input signal includes:

[0029] TTFC status, valid bit status, illegal number status, jump status.

[0030] In at least one embodiment of the present application, in step 2, when the input signal is a discrete signal of an avionics signal, the input signal includes:

[0031] TTFC status, transition status.

[0032] In at least one embodiment of the present application, in step 2, when the input signal is an enumeration signal of an avionics signal, the input signal includes:

[0033] TTFC status, transition status.

[0034] In at least one embodiment of the present application, in step 4, the test runtime is set to be greater than the runtime of the first monitoring and voting test case set.

[0035] In at least one embodiment of the present application, in step 4, comparing the first monitoring voting test results using the test result automatic comparison script includes:

[0036] Import the first monitoring voting test results into the test result automatic comparison script to generate a fixed-format test result comparison chart;

[0037] Determine whether the theoretical value of the first monitoring voting test result is consistent with the actual value according to the test result comparison chart;

[0038] If they are consistent, proceed to step five;

[0039] If they are inconsistent, perform fault location.

[0040] In at least one embodiment of the present application, in step five, the input signal of the second monitoring and voting is divided into: an analog signal, a discrete signal, and an enumeration signal.

[0041] In at least one embodiment of the present application, in step six, when the input signal is an analog signal;

[0042] Input signals include: maximum fault, minimum fault, maximum-second-maximum fault, maximum-minimum fault, second-minimum-maximum fault, 2:2 fault, 1:1:1:1 fault, device status, link status, and valid bit status.

[0043] In at least one embodiment of the present application, in step six, when the input signal is a discrete signal;

[0044] Input signals include: 0 fault, 1 fault, 2:2 fault, device status, link status, and valid bit status.

[0045] In at least one embodiment of the present application, in step six, when the input signal is an enumeration signal;

[0046] Input signals include: maximum fault, minimum fault, maximum-second-maximum fault, maximum-minimum fault, second-minimum-maximum fault, 2:2 fault, 1:1:1:1 fault, device status, link status, and valid bit status.

[0047] In at least one embodiment of the present application, in step eight, the test runtime is set to be greater than the runtime of the second monitoring and voting test case set.

[0048] In at least one embodiment of the present application, in step eight, comparing the second monitoring voting test results using an automatic test result comparison script includes:

[0049] Import the second monitoring voting test results into the test result automatic comparison script to generate a fixed-format test result comparison chart;

[0050] Determine whether the theoretical value of the second monitoring voting test result is consistent with the actual value according to the test result comparison chart;

[0051] If they are inconsistent, perform fault location.

[0052] The invention has at least the following beneficial technical effects:

[0053] The automated testing method for redundancy management software of the present application splits the intermediate links of the redundancy management software into two layers of testing through the first monitoring and voting test case input script and the second monitoring and voting test case input script, which can ensure that the integrity of the test target software is not damaged, and can also simplify the intermediate links and facilitate fault injection; classify the data sources, use test cases to automatically generate scripts, and generate test case sets that meet the needs of different devices, thereby simplifying the repetitive work of test cases; and realize dynamic data comparison of multiple signals at the same time through automatic comparison of test case results, which facilitates fault location. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 This is a flow chart of an automated testing method for redundancy management software according to one embodiment of the present application;

[0055] Figure 2 This is a schematic diagram of a first monitoring and voting test case set in one embodiment of the present application;

[0056] Figure 3 This is a schematic diagram of the first monitoring and voting test results of an embodiment of the present application;

[0057] Figure 4 This is a corresponding relationship diagram of the first monitoring voting and second monitoring voting test inputs in one embodiment of the present application;

[0058] Figure 5 This is a schematic diagram of a second monitoring and voting test case set according to an embodiment of the present application;

[0059] Figure 6 This is a schematic diagram of the second monitoring and voting test results of an implementation method of the present application. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solutions and advantages of the implementation of this application clearer, the technical solutions in the embodiments of this application will be described in more detail below in conjunction with the drawings in the embodiments of this application. In the drawings, the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The described embodiments are part of the embodiments of this application, not all of the embodiments. The embodiments described below with reference to the drawings are exemplary and are intended to be used to explain this application, and should not be understood as limitations on this application. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. The embodiments of this application are described in detail below in conjunction with the drawings.

[0061] In the description of this application, it should be understood that the terms "center", "longitudinal", "lateral", "front", "back", "left", "right", "vertical", "horizontal", "top", "bottom", "inside", "outside", etc., indicating the orientation or position relationship, are based on the orientation or position relationship shown in the accompanying drawings, and are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it should not be understood as limiting the scope of protection of this application.

[0062] The following is combined with Figures 1 to 6 This application is described in further detail.

[0063] This application provides an automated testing method for redundancy management software, comprising the following steps:

[0064] Step 1: According to the interface volume of the requirement specification, classify the input signal into different signal types according to the signal source and intermediate state differences;

[0065] Step 2: For input signals of different signal types, write an automated test case generation script based on the input signal value range, signal fault type, and state fault type to generate the first monitoring and voting test case set for each input signal;

[0066] Step 3: Import the first monitoring and voting test case set into the simulation running environment to drive the redundancy management software to run;

[0067] Step 4: Set the test run time. After the test is completed, use the test result automatic comparison script to compare the results of the first monitoring voting test;

[0068] Step 5: Using the output signal of the first monitoring and voting as the input signal of the second monitoring and voting, and dividing the input signal of the second monitoring and voting into different signal types;

[0069] Step 6: For input signals of different signal types, write an automated test case generation script based on the input signal value range, signal fault type, and state fault type to generate a second monitoring and voting test case set for each input signal;

[0070] Step 7: Import the second monitoring and voting test case set into the simulation running environment to drive the redundancy management software to run;

[0071] Step 8: Set the test running time. After the test is completed, compare the second monitoring voting test results through the test result automatic comparison script to generate a test report.

[0072] In the automated testing method for the redundancy management software of the present application, in step one, first, according to the interface volume of the requirement specification, the input signals are divided into: electromechanical signals, flight control signals, and avionics signals according to the signal source; then, according to the differences in the intermediate states, the input signals of each signal source are divided into: analog signals, discrete signals, and enumeration signals.

[0073] In this embodiment, according to the differences in intermediate states, electromechanical signals are divided into analog signals and enumerated signals; flight control signals are divided into analog signals; and avionics signals are divided into analog signals, discrete signals, and enumerated signals.

[0074] In the automated testing method for the redundancy management software of the present application, in step 2, based on the classification of the input signal in step 1, combined with the value range of the input signal, the signal fault type and the state fault type, a first monitoring voting test case set is generated.

[0075] Specifically, when the input signal is an analog signal of an electromechanical signal, the input signal includes: device status, serdes bus status, CCDL bus status, heartbeat word status, valid bit status, and transition status.

[0076] When the input signal is an enumeration signal of an electromechanical signal, the input signal includes: device status, serdes bus status, CCDL bus status, heartbeat word status, and transition status.

[0077] When the input signal is an analog signal of a flight control signal, the input signal includes: device status, serdes bus status, mode word status, and valid bit status.

[0078] When the input signal is an analog signal of an avionics signal, the input signal includes: TTFC state, valid bit state, illegal number state, and jump state.

[0079] When the input signal is a discrete signal of an avionics signal, the input signal includes: TTFC state and jump state.

[0080] When the input signal is an enumeration signal of an avionics signal, the input signal includes: TTFC state and jump state.

[0081] Furthermore, in step 4, the test run time is set to be longer than the run time of the first monitoring and voting test case set. After the run is completed, the test result automatic comparison script is used to compare the test results of the first monitoring and voting test case set, which includes:

[0082] Import the first monitoring voting test results into the test result automatic comparison script to generate a fixed-format test result comparison chart;

[0083] Determine whether the theoretical value of the first monitoring voting test result is consistent with the actual value according to the test result comparison chart;

[0084] If they are consistent, proceed to step five;

[0085] If they are inconsistent, perform fault location.

[0086] The automated testing method for redundancy management software of the present application, in step 5, uses the output of the first monitoring vote as the input of the second monitoring vote, and divides the input signal of the second monitoring vote into: analog signal, discrete signal, and enumeration signal. In step 6, based on the signal type in step 5, combined with the value range of the input signal, signal fault type, and state fault type, a second monitoring vote test case set for each input signal is generated. Wherein, when the input signal is an analog signal; the input signal includes: maximum value fault, minimum value fault, maximum second maximum fault, maximum minimum fault, second smallest minimum fault, 2:2 fault, 1:1:1:1 fault, device status, link status, and valid bit status. When the input signal is a discrete signal; the input signal includes: 0 fault, 1 fault, 2:2 fault, device status, link status, and valid bit status. When the input signal is an enumeration signal; the input signal includes: maximum value fault, minimum value fault, maximum second maximum fault, maximum minimum fault, second smallest minimum fault, 2:2 fault, 1:1:1:1 fault, device status, link status, and valid bit status.

[0087] In the automated testing method for the redundancy management software of the present application, in step eight, the test run time is set to be greater than the run time of the second monitoring and voting test case set. After the run is completed, the test results of the second monitoring and voting test case set are also compared using the test result automatic comparison script, which includes:

[0088] Import the second monitoring voting test results into the test result automatic comparison script to generate a fixed-format test result comparison chart;

[0089] Determine whether the theoretical value of the second monitoring voting test result is consistent with the actual value according to the test result comparison chart;

[0090] If they are inconsistent, perform fault location.

[0091] According to the test results, analyze the items where the theoretical values ​​are inconsistent with the actual values, and generate a test report attachment in the corresponding format.

[0092] The automated testing method for the redundancy management software of the present application is to divide all signals that need to be monitored and voted into two levels of testing: the first monitoring and voting and the second monitoring and voting. The output result of the first monitoring and voting is used as the input of the second monitoring and voting test; the interface volume of the requirements specification is analyzed to divide the test case input of the first monitoring and voting into three parts according to different sources: electromechanical, flight control, and avionics. Then, according to the difference in intermediate state quantities, the input from different sources is divided into analog signals, discrete signals, and enumeration signals. Then, a test case automatic generation script is used to generate corresponding test cases according to the value range of different input signals, various signal fault types, and state fault types; the test case is imported into the target machine by loading the test script to drive the redundancy management software to run; finally, a dynamic comparison of multiple signals is achieved through the test result automatic comparison script.

[0093] This application aims at the characteristics of manual testing of the redundancy management software of the flight control system, which is repetitive and labor-intensive, and combines the large number of intermediate states of the software to propose an automated testing method for the redundancy management software of the flight control system. This method splits the intermediate state of the software into two layers of testing: the first monitoring vote and the second monitoring vote. It can achieve full coverage that meets the requirements without affecting the software state, and also facilitates the injection of fault states. Test cases with different signal sources are automatically generated through test case script generation, which reduces repetitive work and avoids human test case design errors. The dynamic output result comparison of multiple signals is achieved simultaneously through automatic comparison of test results, which improves work efficiency.

[0094] Figure 1 This is a complete automated test flow chart for the redundancy management software. The specific implementation method is further described in detail below with examples.

[0095] Step 1: Based on the interface volume of the requirement specifications, classify the input signals into electromechanical input, flight control input, and avionics input according to the signal source. Then, based on the difference in fault status, classify the electromechanical input into analog signals and enumerated signals, the flight control input into analog signals, and the avionics input into analog signals, discrete signals, and enumerated signals.

[0096] Step 2: Based on each signal source in step 1, analyze the fuel weight signal of the electromechanical system as an example. Write a test case automatic generation script according to the rule of traversing the device status, serdes link status, CCDL link status, system mode status, and signal status faults in sequence, and generate a set of test cases that meet all fault conditions for the fuel weight signal, such as Figure 2 shown.

[0097] Step 3: Batch load the test case set of all signals generated in step 2 onto the target machine to drive the redundancy management software to run.

[0098] Step 4: After setting the test run time to be longer than the execution time of the test case set for each signal, export the run results to the test result automatic comparison tool to generate a fixed format test result comparison chart to observe whether the theoretical value of the first monitoring vote of fuel weight is consistent with the actual value. The results are as follows: Figure 3 shown.

[0099] by Figure 3 Taking the test results as an example, it can be seen that the theoretical values ​​at the 3rd and 11th fault points do not match the actual values. Corresponding to the test cases, it can be located that the monitoring and voting logic of the device status fault and CCDL link fault parts are incorrect.

[0100] Step 5: Use the signal output of the first monitoring and voting test as the input of the second monitoring and voting test, and divide the input into analog signals, discrete signals, and enumeration signals according to the signal type. The corresponding relationship between the signal input of the first monitoring and voting test and the second monitoring and voting test is as follows: Figure 4 shown.

[0101] Step 6: Taking the fuel weight signal as an example, write a script to generate the second monitoring voting test case according to the rules of traversing the maximum value fault, minimum value fault, maximum second maximum fault, maximum minimum fault, second smallest minimum fault, 2:2 fault, 1:1:1:1 fault, device status fault, link fault, and validity fault in sequence, and automatically generate the fuel weight second monitoring voting test case set, such as Figure 5 shown.

[0102] Step 7: Import the fuel weight second monitoring voting test case set into the simulation running environment to drive the redundancy management software to run.

[0103] Step 8: Set the test run time to be longer than the test case set run time. After the run is completed, import the test results into the test result automatic comparison script for automatic comparison. The results are as follows: Figure 6 shown.

[0104] Based on the test results, we analyzed items where the theoretical and actual values ​​were inconsistent. Taking the first fuel weight monitoring voting value as an example, we found that the voting results were incorrect during the minimum value failure and the 2:2 failure.

[0105] The automated testing method of the redundancy management software of the present application uses different test cases to automatically generate scripts to generate a test case set, which reduces the repetitive work of testers and avoids human errors introduced by testers due to too much test data; the test process is divided into the first monitoring and voting test and the second monitoring and voting test, which achieves a complete test of the requirements without changing the software architecture, and streamlines the intermediate links of the fault state test, making it easier to inject faults; the test case set results of a large number of signals can be automatically compared at the same time through automatic comparison of test results, which saves test time and facilitates fault location; test case records that conform to the format can also be generated as an attachment to the test report. The present application is particularly suitable for functional testing in the early stage and regression stage of the development of the redundancy management software of the flight control system.

[0106] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. An automated testing method for redundancy management software, characterized in that: include: Step 1: According to the interface volume of the requirement specification, classify the input signal into different signal types according to the signal source and intermediate state differences; Step 2: For input signals of different signal types, write an automated test case generation script based on the input signal value range, signal fault type, and state fault type to generate the first monitoring and voting test case set for each input signal; Step 3: Import the first monitoring and voting test case set into the simulation running environment to drive the redundancy management software to run; Step 4: Set the test run time. After the test is completed, use the test result automatic comparison script to compare the results of the first monitoring voting test; Step 5: Using the output signal of the first monitoring and voting as the input signal of the second monitoring and voting, and dividing the input signal of the second monitoring and voting into different signal types; Step 6: For input signals of different signal types, write an automated test case generation script based on the input signal value range, signal fault type, and state fault type to generate a second monitoring and voting test case set for each input signal; Step 7: Import the second monitoring and voting test case set into the simulation running environment to drive the redundancy management software to run; Step 8: Set the test running time. After the test is completed, compare the second monitoring voting test results through the test result automatic comparison script to generate a test report.

2. The automated testing method for redundancy management software according to claim 1, characterized in that: In step 1, according to the interface volume of the requirements specification, the input signals are divided into different signal types according to the signal source and intermediate state differences, including: According to the interface volume of the requirement specification, the input signals are divided into electromechanical signals, flight control signals, and avionics signals according to the signal source; According to the differences in intermediate states, the input signals from various signal sources are divided into: analog signals, discrete signals, and enumeration signals.

3. The automated testing method for redundancy management software according to claim 2, characterized in that: According to the difference in intermediate states, electromechanical signals are divided into: analog signals and enumeration signals.

4. The automated testing method for redundancy management software according to claim 3, characterized in that: According to the differences in intermediate states, flight control signals are divided into: analog signals.

5. The automated testing method for redundancy management software according to claim 4, characterized in that: According to the differences in intermediate states, avionics signals are divided into: analog signals, discrete signals, and enumeration signals.

6. The automated testing method for redundancy management software according to claim 5, characterized in that: In step 2, when the input signal is an analog signal of an electromechanical signal, the input signal includes: Device status, serdes bus status, CCDL bus status, heartbeat word status, valid bit status, and transition status.

7. The automated testing method for redundancy management software according to claim 6, characterized in that: In step 2, when the input signal is an enumeration signal of an electromechanical signal, the input signal includes: Device status, serdes bus status, CCDL bus status, heartbeat word status, and transition status.

8. The automated testing method for redundancy management software according to claim 7, characterized in that: In step 2, when the input signal is an analog signal of a flight control signal, the input signal includes: Device status, serdes bus status, mode word status, valid bit status.

9. The automated testing method for redundancy management software according to claim 8, characterized in that: In step 2, when the input signal is an analog signal of an avionics signal, the input signal includes: TTFC status, valid bit status, illegal number status, jump status.

10. The automated testing method for redundancy management software according to claim 9, characterized in that: In step 2, when the input signal is a discrete signal of an avionics signal, the input signal includes: TTFC status, transition status.

11. The automated testing method for redundancy management software according to claim 10, characterized in that: In step 2, when the input signal is an enumeration signal of an avionics signal, the input signal includes: TTFC status, transition status.

12. The automated testing method for redundancy management software according to claim 11, characterized in that: In step 4, the test runtime is set to be longer than the runtime of the first monitoring voting test case set.

13. The automated testing method for redundancy management software according to claim 12, characterized in that: In step 4, the test results of the first monitoring voting test are compared using the test result automatic comparison script, including: Import the first monitoring voting test results into the test result automatic comparison script to generate a fixed-format test result comparison chart; Determine whether the theoretical value of the first monitoring voting test result is consistent with the actual value according to the test result comparison chart; If they are consistent, proceed to step five; If they are inconsistent, perform fault location.

14. The automated testing method for redundancy management software according to claim 13, characterized in that: In step five, the input signal of the second monitoring vote is divided into: analog signal, discrete signal, and enumeration signal.

15. The automated testing method for redundancy management software according to claim 14, characterized in that: In step six, when the input signal is an analog signal; Input signals include: maximum fault, minimum fault, maximum-second-maximum fault, maximum-minimum fault, second-minimum-maximum fault, 2:2 fault, 1:1:1:1 fault, device status, link status, and valid bit status.

16. The automated testing method for redundancy management software according to claim 15, characterized in that: In step six, when the input signal is a discrete signal; Input signals include: 0 fault, 1 fault, 2:2 fault, device status, link status, and valid bit status.

17. The automated testing method for redundancy management software according to claim 16, characterized in that: In step six, when the input signal is an enumeration signal; Input signals include: maximum fault, minimum fault, maximum-second-maximum fault, maximum-minimum fault, second-minimum-maximum fault, 2:2 fault, 1:1:1:1 fault, device status, link status, and valid bit status.

18. The automated testing method for redundancy management software according to claim 17, characterized in that: In step eight, the test runtime is set to be greater than the runtime of the second monitoring and voting test case set.

19. The automated testing method for redundancy management software according to claim 18, characterized in that: In step 8, the second monitoring voting test results are compared using the test result automatic comparison script, including: Import the second monitoring voting test results into the test result automatic comparison script to generate a fixed-format test result comparison chart; Determine whether the theoretical value of the second monitoring voting test result is consistent with the actual value according to the test result comparison chart; If they are inconsistent, perform fault location.

Images