Rozrobka ta testuvannya h. Test on the topic “software development technology”. What is an emulator and a simulator?

Golovna / Troubleshooting

It is very important to understand that QA is not less than a desperate search for mercy from the software. This process consists of a number of stages that follow practically the entire life cycle of software development: from the analysis and testing of cobs, it was possible to catch and test incidents from the productive environment. This article examines the stages, processes and approaches to testing. In advance, the testing methods will cover a comprehensive topic and will be thoroughly discussed. And now I will highlight the most important steps in the QA process, which require self-awareness and not obviously guess them before going through interviews.

1. Documentation analysis: business benefits from functional specifications

At which stage we understand that we can see on the right. During the process of analyzing documentation, we provide feedback to other team members, such as the analyst and developer, to understand functionality. Often this food allows you to identify any illogical moments in your work, rubbing, a possible negative influx of new ones can affect the current functionality of the software. All these are potential benefits that we can mark and turn off at the documentation stage.

2. Evaluation and testing planning

Based on the knowledge obtained at the analysis stage, we estimate the testing hour. The assessment is also great and important topic, dedicated to the whole section of this supporter ( Vimogi before testing, part 9: assessment of the hour for testing)
Next comes the planning. The report on the planning will be published by the statistics for managers and professional testing groups. Prote, the tester needs to know that at this stage a strategy and test plan are formed (called a test manager), which combines all the information about what functionality we are testing, on what detail, with what data, who takes This is the fate of the process, as vikoryst’s criteria, etc. For more details, see the article about the test strategy. During the interview, the test taker will often ask about the test strategy, what it consists of and what it is needed for. I recommend that you familiarize yourself with the material in order to overcome the problem.

Since the process is highly formalized and includes the absence of reports, reports and other supporting documents, then at this stage we also prepare all the necessary templates for these documents

3. Development of test scenarios

At this stage, we describe the scenarios in which the product is being tested. There are two important topics here: how to identify necessary scenarios and how to describe them.

In order to determine which revisions need to be canceled, there are a number of techniques and methods. In this article, I will not describe them (you can find the report on WiKi by the title), but I will only outline the steps from them:
- Traceability matrix
- Decision Table
- Boundary value analysis and Equivalence partitioning
- Pairwise Technique
- Use-Case

To complete the interview, please contact us first:

How do you plan to mold the overflow?
Can you imagine how much this list of checks covers the functionality that needs to be checked?

If you have not tried any of the techniques before, it will be immediately clear to the interviewer that the knowledge is more theoretical, and you can easily get lost. In this case, it is necessary to understand the method of testing boundary values and equivalence classes (Boundary value analysis and Equivalence partitioning) and follow the PZ function. Make sure to perform at least one test on the skin function of the product. Since the functionality is subject to the complex logic of the robot, then it is necessary to check the skin-mental algorithm. Also, be sure to focus on business sense functionality, on those that PZ in reality will be used-case, creating a test for skin scenarios.

A description of test scenarios or test design can also be carried out without any implementation: from the use of special software such as HP ALM to the description of scenarios in Excel or Word. Here it is important to clearly understand the main parameters of the test, which will always depend on the instrument. It’s better to give you something like this: “What does an ideal test case look like? What is it made of?” The main warehouse tests are as follows:
- Version of the tested software, sent to Vimogi, author of the test case
- Pochatkovі brains, steps for preparation before testing: camp of the system, adjustment of the middle, data
- Title of the test case with its main idea
- Test duration, what to include: performance, evaluation result, actual result
- Status test (here you also need the date for setting the status and who changed it)
- Posilannya on the appearance of amends
- How to turn the system around at the exit stage

Of course, the test case can be used without other parameters, and I know only the most important ones can’t do without them. A more detailed description of the test warehouses can be found here.

4. Vikonannya testuvannya PZ

In-between testing is carried out at several stages, and in the middle of the skin stage - a cycle (testing -> analysis and correction -> retest), or a thorough re-verification of the effectiveness (implementation\functionality works or does not work). For now, let's look at manual testing and automation on a related topic. As the main stages of software testing, as defined by the QA team, you can see the following steps:

Smoke testing and Sanity testing – forward verification of the system and post-production of the software. At this stage, our task is to change so that the test middle is adjusted and processed, and the removal of the blank contains the necessary functionality and changes can be continued with it. That. We are doing basic, basic revisions.
Functional & non-functional testing is the main stage of testing, which includes all the different types of testing of different types of devices in section “3 - Basic knowledge of testing”, directly for change, added as part of the delivery. At this stage we carry out a number of testing cycles, usually more than 2.
Regression testing – we conduct a cycle of regression testing and verify that new features and changes do not break the current functionality. There are also a number of cycles here. In principle, this stage can be combined with another phase of the previous block - Functional & non-functional testing.
Integration & end-to-end testing – at this stage we check how our module, system and product interact with other modules, systems and products. Here we check the entire operation of the operator during the hour of working with the system. For example, a buyer submits an application through the website of an online store, then the application is recorded in the database, then processed and transferred to the system for purchasing. In this case, we need to adjust precisely and check the entire life cycle of the application, since we have only completed one system at Lancius.
Demo testing & User Acceptance Testing – stage of demonstration for the agent/correspondents, who can also (and ideally are responsible for) conduct their own testing of the product – UAT

More detailed stages of testing of the PZ are presented in the diagram Participants in the testing process . There are also other commands that also take part in the testing process so that a better picture emerges.

5. Cultivation of pouches and preparation of test results

At this stage we will do the following:

We carry out a clear and detailed analysis of the problems identified during testing
We formalize the results in terms of testing metrics
We are prepared to report on the results of the test with the viscosity, and it is recommended that this mixture be added before delivery to the products, which are risks, which steps must be followed in order to avoid or minimize failures.

As a result of testing metrics, we can look at the following indicators (report on testing metrics in other statistics):

The number of critical defects is equal to their criticality

For example, we may have clear criteria that with critical defects of the Critical level we are not productive, and a critical defect of the High level may be only one, and thus there may be additional instructions on how to deal with this issue. dkami ta plan usunennya

Number of open defects to total number of defects

So we show which part of the fixes has not been corrected and how many such fixes are in order to praise the decision to continue testing or release the PZ

Number of defects to final number of tests

This metric shows the average effectiveness of one test

The number of times in which the defect was transferred on average

This metric shows the complexity and clarity of the code. If the indicator is high, this means high potential risks, especially if changes will be made to the product over the years

6. Maintenance during installation of the product

At this stage of testing, instruct the support team to install into the product all the necessary information about testing the product, possibly containers, folding devices.

7. Applying hourly care to the product

Like the development process, the process of further software testing also follows the same methodology. Under the methodology in this category we understand different combinations of principles, ideas, methods and concepts that you put into the hour of working on a project.

At this time, it is necessary to reach a large number of different approaches to testing, skin with their own starting points, and trivalities of testing and methods that can be tested at the skin stage. And choosing one or the other of them can be an unforgivable task. In this article we will look at different approaches to software testing and talk about their main features to help you navigate this diversity.

Cascade model (Linear sequential model of the life cycle)

The Waterfall Model is one of the oldest models that can be used not only for development and testing of software, but also practical for any other project. Its basic principle is the sequential order of succession. This means that we can proceed to the deadline for development or testing only after it has been successfully completed. This model is suitable for small projects and can only be designed in such a way that everything can be accurately measured. The main advantages of this methodology are cost-effectiveness, ease of use and documentation management.

The process of testing the PZ begins after completion of the development process. At this stage, all necessary tests are transferred from units to system testing in order to control the operation of components both separately and comprehensively.

In addition to the most important advantages, this approach to testing also has its shortcomings. From now on there will be a possibility of identifying critical defects during the testing process. This may lead to the need to change one of the system components or transfer the entire logic to the project. Although such a task is impossible with a cascade model, the fragments of rotation on the leading edge of this methodology are blocked.

Find out more about the cascade model with advanced statistics.

V-Model (Verification and Validation Model)

As a cascade model, the V-Model technique is based on a direct sequence of cuts. The main difference between these two methodologies is that testing for each phase is planned in parallel with the development stage. Consistently with this PP testing methodology, the process begins to be strictly feasible and becomes possible to print static testing, then. verification and inspection, which allows the elimination of possible defects at later stages. A basic testing plan is created for the skin level of software development, which means the results obtained, as well as the entry and exit criteria for that product.

The diagram of this model shows the principle of dividing the order into two parts. That is due to the design and layout, placement of the left-handed. The area where software security testing is taking place is located right-handedly:

The main steps of this methodology may vary, but may include the following:

Stage vyznachennaya vimog. The best test is carried out at this stage. Its main responsibility lies in assessing the readiness of the system before the final test
Stage in which you are enrolled high-quality design, or High-Level Design (HDL). This stage is carried out before system testing and includes an assessment of the potential before system integration
Detailed design phase(Detailed Design) is parallel until the integration testing phase, during which the interaction between different system components is checked
Afterwards code writing stage Another important task begins - unit testing. It is very important to ensure that the behavior of other parts and components of the software is correct and consistent with the results

The only thing that has been reviewed about the testing methodology is the number of ready-made solutions that could be developed to deal with software defects identified at the testing stage.

Incremental model

This methodology can be described as a multi-stage model for testing the software. The work process is divided into a number of cycles, each of which is also divided into a module. Skin iteration adds additional functionality to the PZ. The increment consists of three cycles:

design that rose
testing
implementation.

This model allows one-hour development of different versions of the product. For example, the first version can go through the testing stage while another version is at the development stage. The third version can go through the design stage at the same time. This process can be continued until the project is completed.

Obviously, this methodology emphasizes identifying the maximum possible number of errors in the tested software as quickly as possible. This is also the implementation phase, which requires confirmation of the readiness of the product before delivery of the final package. All these factors could have increased their capacity before testing.

Adapted from the latest methodologies, incremental model There are a bunch of important achievements. As a matter of fact, changes can be made at a lower cost, and the process of testing the software is more efficient, since it is much easier to carry out testing and debugging in small iterations. Tim is not less, but it means that the secret varity is still greater, lower than the cascade model.

Spiral model

The spiral model is a methodology for testing software, which is based on an incremental approach and prototyping. It consists of four stages:

Planning
Risk analysis
Rozrobka
Evaluation

Immediately after the completion of the first cycle, another begins. Software testing begins at the planning stage and continues to the evaluation stage. The main advantage of the spiral model is that the first test results appear immediately after the test results appear at the third stage of the skin cycle, which helps to guarantee a correct assessment of the skin tone. It is important to remember that this model can be expensive and not suitable for small projects.

Regardless of the fact that this model is old, it will be deprived of cinnamon both for testing and for development. Moreover, the main meta-rich software testing methodologies, including the spiral model, have changed over time. We are not only used to look for defects in the add-ons, but also to explain the reasons that caused them. This approach helps retailers to process orders more effectively and make decisions faster.

Read the report on the spiral model in the previous blog post.

Agile

Agile development and software testing methodology can be described as a set of approaches oriented towards dynamic interactive development, dynamic shaping is possible and ensures their success as a result of steady interaction It is in the middle of a work group that self-organizes. More advanced software development methodologies are aimed at minimizing risks by developing them in short iterations. One of the main principles of this flexible strategy is the ability to quickly respond to possible changes without relying on long-term planning.

Find out more about Agile(Note - English language article).

Extreme Programming (XP, Extreme Programming)

Extreme programming is one of the applications of the software development software. An important feature of this methodology is “peer programming,” a situation where one developer works on the code, while another colleague constantly reviews the written code. The process of testing the software is very important, since it starts earlier, the first row of code is written below. The program module itself is subject to a unit test so that more problems can be corrected at the code writing stage. Another advantage is that the test generates code, and not as a result. This means that the entire portion of the code can only be considered complete if all tests have been successfully passed. Otherwise, the code is modified.

The main advantages of this methodology are consistent testing and short releases, which helps ensure high code integrity.

Scrum

Scrum is part of the Agile methodology, an iterative incremental framework for managing the software development process. Based on the principles of Scrum, the test team can take part in the following stages:

The fate of the Scrum planner
Support for unit testing
Testing the history of koristuvach
Comparison with the product to determine the acceptance criteria
Automatic testing

Moreover, QA participants are expected to be present at all meetings, like other team members, to discuss what was tested and completed yesterday, what will be tested today, as well as the ongoing progress of testing.

At the same time, the principles of Agile methodology in Scrum before the appearance of specific features:

Assessment of the forces necessary for the skin history of the cyst and obligatory
The tester is guilty of being respectful as much as possible, the fragments of the stench can gradually change
The risk of regression increases simultaneously with partial code changes
Simultaneous planning and testing of tests
The inconsistency between team members is often not fully understood by the deputy

Learn more about the Scrum methodology from the latest statistics.

Visnovok

Finally, it is important to note that current practice and other software testing methodologies convey a multiversal approach. In other words, it is not possible to rely on the assumption that one methodology will be applicable to all types of projects. The choice of one of them depends on many aspects, such as the type of project, the capabilities of the lender, the setting of terms, and many others. From the point of view of software testing, it is typical for certain methodologies to start testing at the early stages of development, whereas when working with others it is customary to wait until the system is completely ready.

If you need help with software development or testing, we see a team of development and QA engineers ready to work.

The store's robot is always stocked with ready-made tests for a number of reasons, one of the main ones being the simple availability of clearly laid out tests of different types. Therefore, it is often necessary for investors to develop these or other tests themselves, and then use the method of their folding. We're stuck on these moments.

It is important to know that the creation of standardized tests is a complex and complex process. The tests are carried out by the front robot, which is carried out through their development and testing. When developing tests, three areas are visible: theoretical, practical and experimental (Fig. 3.1.).

The theoretical part of the work includes the development of literature, on the basis of which the development of tests, instead of programs and tools, is possible. Here the structure of the tests, their characteristic features, signs, clear indicators are determined, and the methods of mathematical statistics that will be needed in the experimental part are shown.

During the implementation of the practical stage, there is a preparation of instructions for the test subject on how to carry out testing, the creation of test tasks and test results before them. An important place is assigned to the element-by-element structural and functional analysis of the initial material. As a result, there appear to be elements of knowledge, including knowledge, that are necessary for mastering the initial material and may be of the greatest importance. Therefore, the testers will be careful to include before them the main semantic parts of the beginning, so that they need to understand the meaning, facts, operations, algorithms. Which ensures the stage of formation in scientific various pink operations (analysis, synthesis, concretization, identification, alignment, etc.), from the age-old features of the last. It is important to pay attention to the specific nature of the typical test conditions, on the basis of which variants of test results are developed.

At the practical stage of test development, a rough estimate of the rating scale is made, and the mechanism for transferring the number of points to the resulting rating is examined.

At the practical stage, instructions for the reader and testimonial forms that are tested are also developed.

Table 3.1. Technology for designing didactic tests

Theoretical stage	Practical stage	Experimental stage
1. Purpose of testing 2. Choose your approach before completing the test 3. Introduction to basic material
4. Design of the test structure 5. Development of test orders 6. Examination of test orders 7. Coordination of test orders 8. Design of the test for testing 9. Development of instructive and methodological test preparation 10. Examination of the test
11. Forward testing 12. Analysis and interpretation of test results (assigning clear characteristics to the test)
13. Reworking the gesta based on the results of the preliminary test 14. Folding the remaining dough 15. Standardization of the test (for consumption)

Based on the theoretical and practical stages, there will be an experimental stage of test development. Here the viability of the tests is assessed, the validity of the test form is checked, the statistical characteristics of the subdivided tests are identified, and the suitability of the tests for the intended purposes is determined.

At the experimental stage of development, the test often has to move to the advanced stages, so all three stages - theoretical, practical and experimental - are closely connected with each other and create a one-on-one singing infusion (div. Fig. 3.1.).

The technology for developing didactic tests is presented in more detail in Table 3.1.

The creation of tests is a complex process that involves the work of a team of teachers (methodologists, psychologists, statisticians, etc.), and at the same time the demand for tests, divided by practicing teachers in a given class, is high in schools. In connection with this, readers must adhere to the following recommendations when conducting tests.

Reminder for completing the test

Consider the purpose of testing.

See the knowledge, memory, skills that are identified by the program and provide information about the level of achievement of those or the section that is being viewed.

You can see the test instructions that demonstrate the knowledge, skills and beginners.

4. Predict or see difficult problems objectively (initially) and subjectively (psychologically and methodologically) and identify typical mistakes of students, analyze the reasons for their guilt. Use the robot to fold distractors before testing.

Create a set of test tasks for mastering those.

Conduct an examination of test orders, asking your colleagues to come up with your thoughts about the test.

Carry out the adjustment of test orders at times.

Learn the assessment criteria, the methodology for processing results, and develop a consistent scale from converting a test score to an assessment of school success.

Learn the instructions for writing and instructions for students to work with the test.

Our group has repeatedly discussed development through testing (test-driven development), and most of the comments were overwhelmingly positive from those who supported this methodology. For those who missed it, we collected all the evidence “for” in one article.

Guess what happened to your Test-Drive-Development?

This is a technique for developing software, if the entire development is broken down into a series of small cycles: first, tests are written to make the most of the changes, then the code is written to pass. After this code is refactored, new tests are written as needed. If the test code does not pass, it is corrected.

It sounds amazing. Is it really effective?

Respect everything, yes. First of all, it allows you to more clearly understand what you need to write. And the mind that can be concluded after the robot code – period. The dough itself can be molded according to the technical regulations. If, as a result of writing tests, they begin to super-read themselves - this is the result of reviewing the technical specifications.

Otherwise, as a result of subtasking smaller subtasks, the code becomes much simpler and easier to read. Ideally, there is one assertion per test. Before the same abominations in the designed code (for example, that Vikorist global changes or singletons) call for such a complex test that it encourages the developer not to write it.

Thirdly, the support for the code is almost gone. If, as a result of introducing new functionality or changing old ones, a piece of code begins to function incorrectly, but it will be detected. It is much easier to change the code if the module is broken (and TDD improves program modularity). It is much simpler to inspect code written using the TDD methodology - every step is taken together to implement a clear task, as will be shown in the comments before.

It seems to me that it would be better to write as soon as possible

So, TDD will be taken away from the start at the earliest possible hour. However, if you see the buttons on the right, you will soon be asked to write the first test, and then the code and, perhaps, you will be able to read the code in an hour, even if the process of developing the structures is clear, you will have to answer the question “What should I write?” How to write? Moreover, by spending an hour at a time, you will gain an hour from the next one, greatly reducing your need for the product.

Why is it possible to sens vikoristovvat TDD?

It’s clear that no. TDD is not a panacea. For example, if development is a consequence of experiments, if there is no clear connection to what is most necessary as a result, writing tests will become more of a vantage, which will pull the team back.

Start with what?

A study with an emphasis on testing is based on Kent Beck's distinguished book -

Our work has developed a test kit for testing knowledge on the module: “Recurrent Relationships and Functions” in the course “Discrete Mathematics” based on the eLearning Office 3000 software package of the Hyper Method company, which allows you to combine from a wide range of knowledge basic materials daily electronic beginner courses. The package, in the opinion of its distributors, allows them to minimize time spent on their projects.

The eLearning Office 3000 package includes three components:

EPublisher - for the quick creation of electronic elementary courses;

EAuthor - for the development of distance courses - basic material in a multimedia form, testing systems, full-text search system for materials from the guide and a secure connection with the Web site of the Basic Center;

EBoard – for organizing and managing lectures, seminars, conferences on the Internet.

With the help of eAuthor, you can create a multimedia distance course, which includes three sections: Lectures, Vocabulary and Tests. Lectures can contain text, graphics, sound and video, as well as links to external documents, files and programs. The dictionary allows you to create hypertext links between terms that appear in the text of lectures, and their definitions automatically, according to the rules specified by the author of the course. The tests are designed for students to interactively test their knowledge.

The first paragraph of this section contains descriptions of the software shell tools that allow you to create tests and conduct tests.

In another paragraph there is a short theoretical summary of the material in the section to which the tests are transferred.

Please note that in the third paragraph there are examples of various types of tests created using the eLearning Office 3000 software package, which can be used during computer testing in the “Discrete Mathematics” course.

Functional capabilities of programs for the implementation of various forms of tests and control of student knowledge

2.1 Functional capabilities of programs for the implementation of various forms of tests and control of student knowledge

The preparation of the order for the created tests is transferred to machine processing.

Find programs that will allow you to create an interactive testing system for self-checking students’ knowledge. The eLearning Office 3000 software package is under development

To prepare control meals, select the Test item in the top menu (Fig. 1). When you select this item, a screen appears presenting a window with lists of requests and those that have been entered; Key items: Add food, Edit food, View food, mixers Interchange time and Limit of food with fields for numeric values, as well as standard elements of the window interface of the Designer: round button and positions OK and Close.

Position Add food, click on the menu that appears to select a food option (Fig. 2). Version 1.0 of the Constructor has the following power options: select one or many correct answers from a transfer of up to 5 possible; establishing a subcategory for two lists with up to 5 positions; entering a row of text. In the end, the text row can match the expression up to the case and division characters, as required.

Creation of dough, which may be suitable for different food options, may include the following interface elements:

· Field for entering the name of the section with a list button; you can formulate tests from independent sections, which are obligatory to avoid the topics of the guide;

· Field for entering food text; the food text is either sent directly or imported via the clipboard;

· Fields for entering variants of the type with jumpers in front of them for entering the correct one;

· Fields Sound, Video, Slide for selecting multimedia files for food illustration;

· Field for entering the hour limit for confirmation.

The system that is being tested is created and does not transmit power generation. This is the intention: the system plays the role of a tool for self-verification, which is transferred to the customer on a CD as a warehouse computer assistant. An objective assessment of knowledge must be carried out either through the use of testing systems on the website of the initial training center, or during face-to-face communication with the computer of the remote training system.

Selecting an illustration for the testing system works the same way as when composing a lecture. It is important that, as with other dictionary entries for the glossary, the texts themselves can contain multimedia illustrations. In this case, the text field will be filled in with the help of the clipboard.

The operation of the testing system can be checked immediately after introducing any food through the Test item on the start screen of the handbook.

Menu Testi

The Test menu item is intended for creating and editing test instructions for the initial course.

In this dialog box tests from sections are formed (sections can be combined with lecture sections). For consumption, you can set an hour limit in seconds for one test and limit the number of possible cuts in the dough (Fig. 1). You can create test foods of three types:

· With options to choose from,

· Three row entries,

· for appearance.

To create a new food, you need to select the “Add food” item. When a menu appears, it will drop down in which you will need to select the type of prepared food from the options.

To edit previously created food, select “Edit food”.

To view your food, you need to select the “View food” item.

The ensign “Override the hour” allows you to enclose the hour of the end of everything in its entirety.

The "Limit of sweets" option allows you to determine the maximum number of sweets that can be allowed in the dough.

The choice test allows you to select one or more options based on the food supplied.

The test from the entered row makes it possible to test the response to the appearance of the text row that is entered by the user. In this case, it is possible to verify the entered type against the register and/or division characters.

The test for consistency allows you to set questions in which it is necessary to put the test results in the correct order (for example, put the correct sequence of sequenced actions).

Food with options to choose from. In the Test number field, enter the name of the test block prior to the test being entered. If this block has already been introduced, then its name can be selected from the pool of test blocks. The flow of test blocks can be selected by clicking with the left mouse button on the button that appears in the field for entering the name of the test block.

For power supply you can select one to five options. The skin option is introduced between one row. The correct output options are indicated by clicking the left mouse button on the proportion of the correct input option.

One to five options may be correct. You can limit your meals to an hour. For this purpose, in the entry field the exchange of hour for power supply in seconds is set.

To insert graphic files, you need to select files from the graphics library of the handbook. To do this, you need to click on the select item opposite the words slides. Open the Malyunka dialog box, where you can select the required files.

After pressing the “OK” button, the food will be created and the test dialog box will open, where you can open the test creations by clicking on the mouse.

Nutrition from the introduced row. In the Test number field, enter the name of the test block prior to the test being entered. If this block has already been introduced, then its name can be selected from the pool of test blocks. The flow of test blocks can be selected by clicking with the left mouse button on the button that appears in the field for entering the name of the test block. (Fig.4)

In the Nutrition text field, enter the nutrition text that you need to select. In this case, in this field you can enter not only the food itself, but also a short comment (at the boundaries of the entry field).

The field has the correct response to enter the text row with the correct response to the power supply.

Ensign Vrahovuvat register is placed because it is necessary to check the confirmation not only for consistency with the text, but also for the register in which the confirmation was typed for the students.

Ensign Vrahovuvat divisional signs are placed if it is necessary to check the correspondence to the divisional signs.

To illustrate food, the ability to introduce sound, graphics or video is transferred, but you won’t be able to select graphics and video at the same time (you will have to select one). To insert graphic files, you need to select files from the graphics library of the handbook. To do this, you need to click on the select item opposite the words slides. The “Malyunki” dialog box will appear, where you can select the required files.

Inserting video or audio files is done in the same way.

Power supply. In the Test number field, enter the name of the test block prior to the test being entered. If this block has already been introduced, then its name can be selected from the pool of test blocks. The flow of test blocks can be selected by clicking with the left mouse button on the button that appears in the field for entering the name of the test block. (Fig.5)

In the options field, enter one to five possible items that you need to put in the required order.

In the right column you can indicate items that correspond to the left column (in the correct order)

The field has the correct order of entering the numerical sequence, which confirms the correct order of possible items in the left column to correspond to the right one.

You can limit your meals to an hour. For which clicks on the square, the hour change mode is selected from the Time Interval field. For the input field that appears, the interval between the hour of the response and the power supply in seconds is set.

To illustrate food, the ability to introduce sound, graphics or video is transferred, but you won’t be able to select graphics and video at the same time (you will have to select one).

To insert graphic files, you need to select files from the graphics library of the handbook. To do this, you need to click on the select item opposite the words slides. The “Malyunki” dialog box will appear, where you can select the required files.