Search

Anchor bolts are often used for fixing information boards, supports, and soundproof walls in various facilities. Corrosion of anchor bolts and fatigue cracks occur frequently due to the various external environments, and visual inspection and hammering inspection are mainly used. In visual inspection, it is difficult to confirm corrosion or fatigue cracks of anchor bolts in the area where foundations, nuts, and base plates are installed. Additionally, the hammering inspection is easily affected by the surrounding environment and the subjective reaction of the tester. Therefore, it is necessary to develop a method that can easily and accurately detect defects such as cracks and corrosion occurring in anchor bolts installed in road facilities using non-destructive testing techniques. In this paper, the possibility and reliability of anchor bolt defects such as corrosion and cracks were experimentally verified by applying ultrasonic inspection among non-destructive inspection techniques for anchor bolt maintenance.

U ovom diplomskom radu analizira se učinkovitost i efikasnost ručnog i automatiziranog testiranja na primjeru web aplikacije „Swag Labs“ korištenjem alata za automatizirano testiranje „Playwright“. Daje se prikaz testnih slučajeva za ručno testiranje i testnih skripti za automatizirano testiranje. Temeljem rezultata istraživanja jasno se ističe razlika između navedenih vrsta testiranja te se daje zaključak o najboljim praksama za osiguravanje kvalitete proizvoda. Time se ističe važnost testiranja softvera kao primarnog koraka za osiguravanje kvalitete programskog proizvoda. Osim toga pojašnjavaju se različite metodologije i tehnike testiranja, kao što je testiranje crne, bijele i sive kutije te unakrsno testiranje, jedinično testiranje i regresijsko testiranje. Kako bi se važnost testiranja softvera u potpunosti razumjela prikazana je evolucija testiranja softverskih proizvoda kroz povijest. Time se ukazuje na razliku u testiranju softvera nekad i danas te se zaključuje da osiguravanje kvalitete programskog proizvoda ovisi o uključivanju testiranja od najranijih faza razvoja softvera. This thesis analyzes the effectiveness and efficiency of manual and automated testing on the example of the web application "Swag Labs" using the automated testing tool "Playwright". Test cases for manual testing and test scripts for automated testing are presented. Based on the results of the research, the difference between the mentioned types of testing is clearly highlighted, and a conclusion is given on the best practices for ensuring product quality. This highlights the importance of software testing as a primary step for ensuring the quality of a software product. In addition, various testing methodologies and techniques are explained, such as black, white, and gray box testing, as well as cross-testing, unit testing, and regression testing. In order to fully understand the importance of software testing, the evolution of software product testing throughout history is presented. This indicates the difference in software testing then and now, and it is concluded that ensuring the quality of the software product depends on the inclusion of testing from the earliest stages of software development.

Information is more susciptible than ever, and each technology advancement creates a new security issue that necessitates a new approach to solving the problem. Penetration testing is used to assess the security of an IT infrastructure by exposing its vulnerabilities in a safe manner. It also aids in acquiring access to the effectiveness of existing defense systems, tactics, and policies. The Penetration testing is carried out on a regular basis in order to detect and control risks to achieve ethics to be possessed by the testing crew involved in penetration test. This research uses a qualitative research methodology for investigating manual testing and automated testing. It further aims at critically investigation penetration testing and its importance with tools available for it. KEYWORDS: IT Security, Penetration test, IT governance, Vulnerability assessment.

Testiranje softvera postupak je utvrđivanja da softver ne sadrži greške. Dvije su vrste, ručno i automatizirano. Ručno testiranje softvera razvojem dodatnih značajki softvera postaje neisplativo i dugotrajno; kako bi se skratilo vrijeme testiranja uvodi se automatizirano testiranje. Za razvoj automatiziranih testova potreban je alat. Cypress je alat za razvoj automatiziranih testova i automatizirano testiranje internet aplikacija i stranica. U cypress alatu razvijena je biblioteka s dodatnim funkcijama za brži i lakši razvoj automatiziranih testnih slučajeva. Korištenje je prikazano na primjeru internet aplikacije Software testing is an act of determining that software does not contain errors. There are two types of testing, manual and automated. Manual software testing becomes unprofitable and takes too long to execute while software gets new features. To shorten time needed for testing, automated testing is introduced. For developing automated test there is a need of a tool. Cypress is a tool for developing and running automated tests for Internet apps and websites. Cypress is used to develop new library of advanced function that can be used to speed up and ease up development of automated tests. Example of its use is shown on Internet app

The types of the testing methods were analyzed from the side of development. If changes are made to the code, even minor ones, bugs can appear anywhere in the system. The cost of fixing bugs increases with the time they are discovered. Using effective web testing can prevent unexpected costs. Modern web applications are indeed a place where all the type of the testing is vital for the high-quality product. At the moment, traditional front and back office applications are increasingly moving from desktop computers to web interfaces, so testing web applications is becoming extremely relevant. Thus, learning what to automate and how is an important component of successful web application testing. Web application testing is a software practice that is designed to ensure quality by verifying that the functionality of a particular web application works correctly or according to fixed requirements. Web testing makes it possible to find bugs at any point in time, before release or on a daily basis. On the one hand there are wide range of tools that could be used to pursue this goal by means of using best decisions present for now but on the other hand there are essential advantages and disadvantages present in these tools, which are all in the approach to it, so there are always cons and pros of using one or another. For now, despite on having the ability to test using both black and white box testing it looks like the second one is not the best choice. There are several points on each board for both of them, but black box approach that is being represented with react testing library is more successful and efficient way to cover and application with high- and low-level tests, that could be easily maintained and understood. But white box testing is now the most used decision due to the historic development of the industry. So, it also has some great features and could be chosen to be used on the project, but it should be precise choice with the understanding of all the consequences standing behind., Види методів тестування були проаналізовані з боку розробки. Якщо в код вносяться зміни, навіть незначні, помилки можуть виникнути будь-де системі. Вартість виправлення помилок зростає з часом їх виявлення. Використання ефективного веб тестування може запобігти непередбаченим витратам. Сучасні веб застосування дійсно є місцем, де весь тип тестування є життєво важливим для якісного продукту. На даний момент традиційні фронт та бек-офісні програми все частіше переходять з настільних комп’ютерів на веб інтерфейси, тому тестування веб застосувань стає вкрай актуальним. Таким чином, вивчення того, що і як автоматизувати, є важливим компонентом успішного тестування веб застосувань. Тестування веб застосувань є практикою програмного забезпечення, яка призначена для забезпечення якості за рахунок перевірки того, що функціональні можливості певного веб програми працюють правильним чином або відповідно до зафіксованих вимог. Веб тестування дає можливість знаходити помилки в будь-який час, до релізу або щодня. З одного боку, є широкий спектр інструментів, які можна було б використовувати для досягнення цієї мети за допомогою використання найкращих рішень, присутніх на даний момент, але з іншого боку, є суттєві переваги і недоліки, присутні в цих інструментах, які всі в підході до нього, тому завжди є мінуси і плюси використання того чи іншого. Поки що, незважаючи на можливість тестування з використанням як чорної, так і білої скриньки, останній метод має багато недоліків та не рекомендується до використання. Ці два методи мають місце бути у окремих проєктах, але підхід чорної скриньки, який представлений бібліотекою тестування React є найбільш успішним і ефективним способом покрити і застосування з високими і низькими тестами, які можна легко підтримувати і розуміти. Але тестування білої скриньки в даний час є найбільш вживаним рішенням у зв’язку з історичним розвитком галузі. Отже, воно також має деякі позитивні риси і може бути обрано, щоб бути використаним на проєкті, але повинно бути точним вибором з розумінням всіх наслідків, що за ним слідують.

В роботі визначено фактори, що впливають на проектування та якість відтворення веб-ресурсів, систематизовано технології створення веб-ресурсів та види їх тестування, проведено експериментальне дослідження автоматизованого та ручного тестування, увиразнено процедуру тестування веб-ресурсів, розроблено тест-кейс для перевірки веб-сторінок, досліджено час, потрібний для розроблення односторінкових веб-ресурсів. Надано рекомендації з особливостей наповнення контентом веб-сторінок для найшвидшого їх відтворення на пристроях користувачів. The paper identifies the factors influencing the design and reproduction of web resources, systematizes technologies for creating web resources and types of testing, conducted an experimental study of automated and manual testing. Typical page structures have been developed for selected species. The procedure for testing web resources was clarified, a test case to verify web pages was developed, the time required to develop one-page web resources was explored. Recommendations on the features of filling the content of web pages for the fastest playback on users’ devices were developed.

This article analyzes the existing applications that implement block texture compression algorithms. Based on it, the most optimal variant of technical implementation is introduced. A set of technologies for the implementation of the prototype is selected and substantiated and its architecture is developed on the basis of the principles that ensure the maximum extensibility and purity of the code. With the development of technology and the integration of computerized systems into all possible areas of human activity, more and more software with three-dimensional graphics is being used. Such programs have long since ceased to be used only in the entertainment field for tasks such as computer game development or special effects for cinema. Now with their help doctors can plan the most complex operations, architects check the developed plans of constructions and engineers to model prototypes without use of any materials. On the one hand, such a rapid increase can be explained by the increase in the power of components for personal computers. For example, modern graphics processors, which play a key role in the operation of graphics software, have become much faster in recent decades and have increased their memory hundreds of times. However, no matter how many resources the system has, the question of their efficient use still remains. It is to solve this problem that block texture compression algorithms have been created. In fact, they made it possible to create effective software when computer resources were still quite limited. And with increasing resources allowed to develop software with an incredible level of detail of the models, which led to its active implementation in such demanding areas as medicine, construction and more. The end result of this work is a developed application that takes into account the modern needs of the user. During the development, the most modern technologies were used for the highest speed and relevance of the application. The main advantages and disadvantages of existing solutions were also taken into account during the development. The capabilities of the system were tested using manual testing on a local machine.

The peculiarities of software product testing processes while working in the Scrum-team were studied. The types of testing characteristic of the flexible testing technique are singled out, that make it possible to make the testing process constantly integrated into teamwork, both at the stage of requirements formation and design, and at the stage of coding and generation of test sets. This is possible by making the tester's recommendations in the process of creating user stories, planning the release of the software version in terms of testing and defects, planning a sprint based on user stories and defects, performing a sprint with continuous testing, regression testing after sprint ends and reporting of results of testing. The article highlights the stages of the flexible testing process in the Scrum team. It is proposed to automate the process of flexible testing for a training team project in the Visual Studio software environment based on Team Foundation Server. Author demonstrates an example of automation of the process of flexible testing by dividing it into four quadrants to comply with the principles of working on a flexible methodology of software development. In the first quadrant there is a study of the quality of the internal code of the software product, the modular testing. To implement modular testing in Visual Studio, a new solution is created in order to generate a class for testing, where the conditions for testing are prescribed in the body of the class. The second quadrant implements the principles of system testing. At this stage the features of creating such a test artifact as test cases are demonstrated. That provides for the fulfillment of certain conditions to verify the functionality of the developing software product; linking between created test cases to user stories presented as team project tasks Product Backlog. The study demonstrates an example of manual testing using a special tool Microsoft Test Manager, which allows you to create plans, add and update test cases, perform manual tests. In the third quadrant, it was performed a trial test in Microsoft Test Manager and it was created another test artifact - error reports. The fourth quadrant automatically tests non-functional software requirements.

The aerospace industry has established the Automated Fiber Placement process as a common technique for manufacturing fibre reinforced components. In this process multiple composite tows are placed simultaneously onto a tool. Currently in such processes manual testing requires often up to 50% of the manufacturing duration. Moreover, the accuracy of quality assurance varies significantly with the inspector in charge. Thus, inspection automation provides an effective way to increase efficiency. However, to achieve a proper inspection performance, the segmentation of layup defects need to be examined. In order to improve such defect detection systems, this paper performs a comprehensive ranking of segmentation techniques. Thus, 29 statistical, spectral and structural algorithms from related work were evaluated based on nine substantial criteria as assessed from literature and process requirements. For reasons of determinism and easy technology transferability without the need of much training data, the development of new Machine Learning algorithms is not part of this paper. Afterwards, seven of the most auspicious algorithms were studied experimentally. Therefore, laser line scan sensor depth maps from fibre placement defects were utilised. Furthermore noisy images were generated and applied for testing algorithm robustness. The test data contained five defect categories with 50 samples per class. It was concluded that Adaptive Thresholding and Cell Wise Standard Deviation Thresholding work best yielding detection accuracies mostly $$> 97$$ > 97 %. Noteworthy is that influenced input data can affect the detection results. Feasible algorithms with sensible parameter settings were able to perform reliable defect segmentation for layed material.

The financial reports of the automotive companies' are measured in a standardized manner; therefore, they are transparent and comparable to each other, but this is not valid for the sustainability reports and it is not possible to compare their sustainability performances. Standard-setting organizations are currently searching for better reporting procedures. This study aims to investigate the connection between sustainability and financial reports for the most dominant European car manufacturers. It reviews the traceability of the sustainability elements back to the financial statements, which helps transparency, comparability, and impact measurement of the disclosed items and issues. This investigation allowed us to additionally review whether these companies are targeting to disclose the most harmful pollution impacts, or only focus to disclose the required obligatory items. Given the financial and sustainability reports magnitude manual testing would not provide complete and proper coverage, therefore we utilized an automated and AI-assisted content analysis with natural language processing. In this new review method, the sustainable elements of the textual reports were automatically retrieved following the 5-stage model of Landrum & Ohsowski (2018). The study highlights the lack of true sustainability information content of reports and the potential discrepancies and connections between the financial and the sustainability reports. Findings concluded that sustainability disclosures at the reviewed companies from several aspects could be improved and quantified, traced back to the financial disclosures, and to be comparable to each other if they apply a similar review method. Graphic abstract

Usually, planning a software testing requires solving the basic dilemma: how to provide quality of testing and spend optimal amount of resources. Typically, resources include components such as personnel, software, technical equipment, time, consumables and others. The Armed Forces of Ukraine have the same problems in planning and testing of programs that are expected to be used in the interests of troops and arms command and control. Testing can be performed by manual method and computer-aided method. The computer-aided method is faster but has its drawbacks. In particular, this method requires the development and then verification of a special program that will be involved in testing. In addition, this program may not detect certain problems that a person can notice. Therefore, the authors of the article propose to use the method of manual testing. It is proposed to apply a rational approach for reducing the time for planning and testing using this method. It refers to a significant reduction in the range of input values which will be checked. This approach provides a high quality testing program at the same time. The approach is based on the fact that the range (or list) of all possible values of each input variable is divided into several groups (equivalence classes). The separation is carried out by the principle that each equivalence class includes such input values, which will give the similar results after processing them by program. This approach is widely used by experts in the field of testing. It also meets the standards requirements applicable in Ukraine. There are two general classes of equivalence: accepted values and nonaccepted values. Each of them is divided into more specific ones. The separation is done leaning upon knowledge, skills and predictions of a specialist who is planning the testing. This article provides an example of dividing the input values of four variables into equivalence classes. The approach proposed by the authors of the publication allows to perform software testing faster and more rationally. It is assumed that such a method should be used during testing software that is intended to be used in the interests of the Armed Forces of Ukraine.

In nuclear power plant (NPP), the digital control system introduced nuclear safety software, whose fault tolerance and reliability directly affect the safety of nuclear power plant facilities. Current manual, simulation and testing strategies all have limitations. An effective method to test the system with software plays an important role to ensure the safe operation of NPP. In this paper, a digital control system software test strategy based on real platform is proposed. Taking the RPS system as an example, this strategy analyzes the system function and software logic path characteristics, then identifies the system state by threshold boundary analyzing, and designs a test method based on the random combination of logical combination paths and parameter value intervals, and builds a real platform test environment. This paper has tested the typical functions of Pressurized water reactor (PWR) protection system. The test results show that the test strategy has significantly improved the coverage of paths and parameters. Compared with manual testing, test efficient has been improved obviously in this test platform. At present, this strategy solves the problem of the low efficiency in manual testing, low real-level in simulation testing, and the insufficient coverage in simple automated testing strategy. This strategy also provides good practice for the control system testing and lays the foundation for the reliability evaluation of the system and software.

A drug–drug interaction or drug synergy is extensively utilised for cancer treatment. However, prediction of drug–drug interaction is defined as an ill‐posed problem, because manual testing is only implementable on small group of drugs. Predicting the drug–drug interaction score has been a popular research topic recently. Recently many machine learning models have proposed in the literature to predict the drug–drug interaction score efficiently. However, these models suffer from the over‐fitting issue. Therefore, these models are not so‐effective for predicting the drug–drug interaction score. In this work, an integrated convolutional mixture density recurrent neural network is proposed and implemented. The proposed model integrates convolutional neural networks, recurrent neural networks and mixture density networks. Extensive comparative analysis reveals that the proposed model significantly outperforms the competitive models.

Automation of test data generation is of prime importance in software testing because of the high cost and time incurred in manual testing. This paper proposes an Improved Crow Search Algorithm (ICSA) to automate the generation of test suites using the concept of mutation testing by simulating the intelligent behaviour of crows and Cauchy distribution. The Crow Search Algorithm suffers from the problem of search solutions getting trapped into the local search. The ICSA attempts to enhance the exploration capabilities of the metaheuristic algorithm by utilizing the concept of Cauchy random number. The concept of Mutation Sensitivity Testing has been used for defining the fitness function for the search based approach. The fitness function used, aids in finding optimal test suite which can achieve high detection score for the Program Under Test. The empirical evaluation of the proposed approach with other popular meta-heuristics, prove the effectiveness of ICSA for test suite generation using the concepts of mutation testing.

The article describes the process of mechanical correction of cold-formed fittings produced in coils on industrial rightsized cutting machines of rotary and roller types. The main qualitative characteristics of the reinforcement are given, such as: ultimate tensile strength, offset yield stress, the ratio of ultimate tensile strength offset yield stress, conditional yield strength, total elongation at maximum load and the relative area of crumpling. To assess the effect of mechanical correction on the properties of cold-formed periodic profile fittings, statistical data is used for testing samples of fittings produced in coils and straightened before manual testing and samples of the same fittings transferred from consumer companies after mechanical correction on right-sized rotary type cut machines.Tensile testing of samples was performed on testing machines in the laboratory of physical and mechanical tests No. 3 of the OJSC «BSW – Management Company of the Holding «BMC» in accordance with the requirements of ISO 15630-1:2010 «Steel for concrete reinforcement and pre-stressing. Test method. Part 1. Reinforcing rods, wire rod and wire» and ISO 6892:2016 «Metal Materials. Tensile test. Part 1. Method of test at ambient room temperature».

Construction of Non-Habitable Homes (RTLH) is a government program managed by thesupervision of the Social Service (Dinas Sosial) in the form of housing construction assistancefunds for the poor. In its realization, assistance is still often found to be lacking on target. It isbecause the determination of beneficiaries is not correctly selected, and there are no standardmethods based on existing criteria. These problems require a system that can providerecommendations that conform to clear standards and use techniques that accounted. FuzzySimple Additive Weighting (SAW) method is one method used in decision making. This methodcalculates criteria to get ranking weights to support decision making. The process of selectingcriteria and determining fuzzy variables carried out as a primary process in this method. Afterthe fuzzification weight value obtained, ranking done to use as a reference in the decision makingof recipients. Based on the results of manual testing, the system made is under the effects ofmanual calculations with a level of accuracy reaching 100%, so that implemented as a basis formaking decisions. While testing, the black box system found that all the requirements tested canrun following the overall system functionality. With this recommendation system, it can help thedecision to find the recipients of the Fund for Non-Occupable Homes Construction Assistanceso that it is more targeted.

Web applications displayed on heterogeneous platforms and have a frequently changing life cycle. There is a high demand for their visual testing. This paper presents an approach for automated visual regression testing. The basic concepts of visual testing are discussed. The traditional, manual testing checks the displayed content of various browsers and platforms. This is a huge amount of monotonous work, which often results in human mistakes thus reducing reliability and consistency. Another disadvantage of the manual testing is that it is slow. Certain web applications have weekly updates, manual testing is not a feasible option for them. Automation would gain us consistency and be free from human errors. Obviously, the configuration of the test environment takes some effort but that could return on long term. The paper investigates testing time and reliability of automated visual regression testing in a selected environment.

Tracking API calls of an Android application (app) has significant value for deeply understanding the app's running behaviors, so that to detect security damages, sensitive information leakages, energy consumptions, system resources occupations of the app, etc. However, existing methods track API calls of a target app through launching and manipulating the app in a real or simulated operating environment. The entire process is time consuming, which leads to low efficiency for practical system executing batch analysis for a considerable scale of apps. In order to enhance the speed of API calls tracking, in this paper, we propose a static analysis method, called EstiDroid, to estimate API calls of Android apps by statically analyzing the apps without actually running them. EstiDroid is composed of a static analyzer and an estimation algorithm. To analyze a target app, EstiDroid first obtains several types of static information from the app's.APK file via the static analyzer, then, the estimation algorithm is employed to establish the estimation model for the app based on the static information. Finally, according to the model, the proportion of each API's calls in the total number of calls is estimated. In experiments, 300 apps are tested via EstiDroid and manual operation in smartphone, the results show that EstiDroid only consumed 49242ms on average compared with manual testing, and it reached 84.06% average similarity and 90.74% maximum similarity compared with the API calls tracked in real environments.

The types of the testing methods were analyzed from the side of development. If changes are made to the code, even minor ones, bugs can appear anywhere in the system. The cost of fixing bugs increases with the time they are discovered. Using effective web testing can prevent unexpected costs. Modern web applications are indeed a place where all the type of the testing is vital for the high-quality product. At the moment, traditional front and back office applications are increasingly moving from desktop computers to web interfaces, so testing web applications is becoming extremely relevant. Thus, learning what to automate and how is an important component of successful web application testing. Web application testing is a software practice that is designed to ensure quality by verifying that the functionality of a particular web application works correctly or according to fixed requirements. Web testing makes it possible to find bugs at any point in time, before release or on a daily basis. On the one hand there are wide range of tools that could be used to pursue this goal by means of using best decisions present for now but on the other hand there are essential advantages and disadvantages present in these tools, which are all in the approach to it, so there are always cons and pros of using one or another. For now, despite on having the ability to test using both black and white box testing it looks like the second one is not the best choice. There are several points on each board for both of them, but black box approach that is being represented with react testing library is more successful and efficient way to cover and application with high- and low-level tests, that could be easily maintained and understood. But white box testing is now the most used decision due to the historic development of the industry. So, it also has some great features and could be chosen to be used on the project, but it should be precise choice with the understanding of all the consequences standing behind. Види методів тестування були проаналізовані з боку розробки. Якщо в код вносяться зміни, навіть незначні, помилки можуть виникнути будь-де системі. Вартість виправлення помилок зростає з часом їх виявлення. Використання ефективного веб тестування може запобігти непередбаченим витратам. Сучасні веб застосування дійсно є місцем, де весь тип тестування є життєво важливим для якісного продукту. На даний момент традиційні фронт та бек-офісні програми все частіше переходять з настільних комп’ютерів на веб інтерфейси, тому тестування веб застосувань стає вкрай актуальним. Таким чином, вивчення того, що і як автоматизувати, є важливим компонентом успішного тестування веб застосувань. Тестування веб застосувань є практикою програмного забезпечення, яка призначена для забезпечення якості за рахунок перевірки того, що функціональні можливості певного веб програми працюють правильним чином або відповідно до зафіксованих вимог. Веб тестування дає можливість знаходити помилки в будь-який час, до релізу або щодня. З одного боку, є широкий спектр інструментів, які можна було б використовувати для досягнення цієї мети за допомогою використання найкращих рішень, присутніх на даний момент, але з іншого боку, є суттєві переваги і недоліки, присутні в цих інструментах, які всі в підході до нього, тому завжди є мінуси і плюси використання того чи іншого. Поки що, незважаючи на можливість тестування з використанням як чорної, так і білої скриньки, останній метод має багато недоліків та не рекомендується до використання. Ці два методи мають місце бути у окремих проєктах, але підхід чорної скриньки, який представлений бібліотекою тестування React є найбільш успішним і ефективним способом покрити і застосування з високими і низькими тестами, які можна легко підтримувати і розуміти. Але тестування білої скриньки в даний час є найбільш вживаним рішенням у зв’язку з історичним розвитком галузі. Отже, воно також має деякі позитивні риси і може бути обрано, щоб бути використаним на проєкті, але повинно бути точним вибором з розумінням всіх наслідків, що за ним слідують.

The worldwide shortage of natural sand has created a need for improved methods to create a replacement product. The use of vertical shaft impact (VSI) crushers is one possible solution, since VSI crushers can create particles with a good aspect ratio and smooth surfaces for use in different applications such as in construction. To evaluate the impact a VSI crusher has on the process performance, a more fit-for-purpose model is needed for process simulations. This paper aims to present a modelling framework to improve particle breakage prediction in VSI crushers. The model is based on the theory of energy-based breakage behavior. Particle collision energy data are extracted from discrete element method (DEM) simulations with particle velocities, i.e., rotor speed, as the input. A selection&ndash, breakage approach is then used to create the particle size distribution (PSD). For each site, the model is trained with two datasets for the PSDs at different VSI rotor tip speeds. This allows the model to predict the product output for different rotor tip speeds beyond the experimental configurations. A dataset from 24 different sites in Sweden is used for training and validating the model to showcase the robustness of the model. The model presented in this paper has a low barrier for implementation suitable for trying different speeds at existing sites and can be used as a replacement to a manual testing approach.

Android apps are GUI-based event-driven software and have become ubiquitous in recent years. Obviously, functional correctness is critical for an app’s success. However, in addition to crash bugs, non-crashing functional bugs (in short as “non-crashing bugs” in this work) like inadvertent function failures, silent user data lost and incorrect display information are prevalent, even in popular, well-tested apps. These non-crashing functional bugs are usually caused by program logic errors and manifest themselves on the graphic user interfaces (GUIs). In practice, such bugs pose significant challenges in effectively detecting them because (1) current practices heavily rely on expensive, small-scale manual validation (the lack of automation); and (2) modern fully automated testing has been limited to crash bugs (the lack of test oracles). This paper fills this gap by introducing independent view fuzzing, a novel, fully automated approach for detecting non-crashing functional bugs in Android apps. Inspired by metamorphic testing, our key insight is to leverage the commonly-held independent view property of Android apps to manufacture property-preserving mutant tests from a set of seed tests that validate certain app properties. The mutated tests help exercise the tested apps under additional, adverse conditions. Any property violations indicate likely functional bugs for further manual confirmation. We have realized our approach as an automated, end-to-end functional fuzzing tool, Genie. Given an app, (1) Genie automatically detects non-crashing bugs without requiring human-provided tests and oracles (thus fully automated); and (2) the detected non-crashing bugs are diverse (thus general and not limited to specific functional properties), which set Genie apart from prior work. We have evaluated Genie on 12 real-world Android apps and successfully uncovered 34 previously unknown non-crashing bugs in their latest releases — all have been confirmed, and 22 have already been fixed. Most of the detected bugs are nontrivial and have escaped developer (and user) testing for at least one year and affected many app releases, thus clearly demonstrating Genie’s effectiveness. According to our analysis, Genie achieves a reasonable true positive rate of 40.9%, while these 34 non-crashing bugs could not be detected by prior fully automated GUI testing tools (as our evaluation confirms). Thus, our work complements and enhances existing manual testing and fully automated testing for crash bugs., Proceedings of the ACM on Programming Languages, 5 (OOPSLA), ISSN:2475-1421

Testiranje je neophodno pri osiguravanju kvalitete softvera. Vodeći se načelima testiranja poboljšava se učinkovitost i usredotočenost pri testiranju. Postoje četiri glavne razine testiranja: testiranje komponente, integracijsko testiranje, testiranje sustava i provjera prihvatljivosti. Vrste testiranja razlikuju se po ciljevima testiranja te se dijele na funkcionalno, nefunkcionalno, strukturno te regresijsko i ponovno testiranje. Automatizirano testiranje predstavlja neprestano izvođenje niza testova iznova bez potrebe za ručnim izvršavanjem. Cilj automatiziranog testiranja je smanjiti broj testnih slučajeva koji se trebaju ručno izvoditi, a ne eliminirati ručno testiranje. Cypress je alat za pouzdano testiranje svega što se pokreće u web pregledniku. Testni slučajevi koji se mogu i trebaju automatizirati su oni koji se često ponavljaju i koji oduzimaju puno vremena. Testing is required in software quality assurance. Guided by the testing principles the focus and the efficiency of testing improves. Stages of manual testing include unit testing, integration testing, system testing and acceptance testing. Types of testing differ according to testing objectives and are divided into regression and retesting, functional, non-functional and structural testing. Automated testing is the continuous performance of series of tests repeatedly conducted without the need for manual execution. The goal of automated testing is not to eliminate the manual testing, but to narrow down the number of tests that need to be executed manually. Cypress is a tool for reliably testing anything that runs in web browser. Test cases that can and need to be automated are the ones that are often repeated and time-consuming.

Manual software testing is tedious and costly as it involves significant human effort. Yet, it is still widely applied in industry and will be in the foreseeable future. Although there is arguably a great need for optimization of manual testing processes, research focuses mostly on optimization techniques for automated tests. Accordingly, there is no precise understanding of the practices and processes of manual testing in industry nor about pitfalls and optimization potential that is untapped. To shed light on this issue, we conducted a survey among 38 testing professionals from 16 companies, to investigate their manual testing processes and to identify potential for optimization. We synthesize guidelines when optimization techniques from automated testing can be implemented for manual testing. By means of case studies on two industrial software projects, we show that fault detection likelihood, test feedback time and test creation efforts can be improved when following our guidelines.

Traditional testing methods for mobile apps focus on detecting execution errors. However, the evolution of mobile networks toward 5G will require additional support for app developers to also ensure good performance and user experience. Manual testing in a number of scenarios is not enough to satisfy the expectations of the apps’ end users. This paper presents the testing framework developed in the TRIANGLE project (https://www.triangle-project.eu/), which integrates a complete mobile network testbed to test, benchmark and certify mobile apps. In this paper, we focus on a recent extension of the TRIANGLE framework that uses model-based testing based on model checking to support the automatic generation of user interactions. We introduce the complete testing framework and the basis of the model-based extension. Finally, we use the testing framework to evaluate the performance of the ExoPlayer app in different network scenarios. ExoPlayer is a video streaming app for Android that implements different adaptive streaming protocols.

Due to The complexity of modern software projects and the increasing size of software systems, it becomes difficult to manually perform tests with limited resources. Also, manual testing cannot assure that the software is tested using all possible combinations of inputs. Therefore, automate software testing activities have become primordial in the Software Development Life Cycle (SDLC). Model-based testing is a prominent validation technique in software testing that uses models of the system under test to automatically generate test cases; this generation leads to a large number of test cases; which cannot exhaustively be executed, due to time and cost constraints. Moreover, the test-cases execution order has an influence on the rate at which faults can be detected. Therefore, it is essential to prioritize test cases in order to execute the most important with limited time and cost. On the other hand, The Failure Mode and Effects Analysis (FMEA) considered as one of the formal techniques to do risk based testing. It offers a structured methodology to identifying the system failure modes, analyzing their effects and setting up controls to risk reducing and improve the quality of systems or products. By applying such a technique to Model-based testing projects, we can benefit from FMEA analysis and the automating in same project. Through this paper, we introduced a new model based testing approach for prioritizing and ranking test cases according to the requirements and failure modes. In the suggested approach we used the Failure Mode and Effect Analysis methodology in model based testing way to automatically generate a set of pair {test case, priority number} to prioritize test cases. It differs from existing approaches in that it generates two types of test cases; requirement-based test cases and failure mode-based test cases. For the purpose of experimental evaluation and analysis, we will compare the suggested approach with some well-known prioritization methods and we will present a case study to illustrate the potential application of the proposed approach in a future work.

The paper identifies the factors influencing the design and reproduction of web resources, systematizes technologies for creating web resources and types of testing, conducted an experimental study of automated and manual testing. The technological process of development and testing of the business card site and two one-page web resources was studied in the work. In particular, the modes and parameters of creating and testing web resources have changed. Among the modes and parameters of testing for the study were selected as follows: page size of the web resource, the number and size of requests to the server, the complexity of the object model document (DOM) and its manipulation, the presence and indicators of problems with JavaScript content, Cascading Style Sheet (CSS) complexity and related issues, font characteristics, and page load speeds. Typical page structures have been developed for selected species. The procedure for testing web resources was clarified, a test case to verify web pages was developed, the time required to develop one-page web resources was explored. Recommendations on the features of filling the content of web pages for the fastest playback on users’ devices were developed. To speed up the loading time, it is recommended to optimize the components of the page, using technology in which all efforts go first to load the main components, and the material that goes below the page is loaded when the user views the page. The most optimized pages are created using Tilda.cc, and the worst option, of those studied, is Bitrix24. Tilda.cc has advantages in speed, but also has a number of disadvantages. Tilda.cc is not a universal system and is designed more to create one-page web resources. WordPress is a more versatile system that allows you to create more complex web resources, and create and place on the page non-standard, personalized blocks, which, in turn, provides greater variability of the resulting web resources. In terms of performance, with the connection of special plug-ins, information optimization operations, you can achieve results even better than Tilda. To save time, it is advisable to create web pages using online designers., В роботі визначено фактори, що впливають на проектування та якість відтворення веб-ресурсів, систематизовано технології створення веб-ресурсів та види їх тестування, проведено експериментальне дослідження автоматизованого та ручного тестування, увиразнено процедуру тестування веб-ресурсів, розроблено тест-кейс для перевірки веб-сторінок, досліджено час, потрібний для розроблення односторінкових веб-ресурсів. Надано рекомендації з особливостей наповнення контентом веб-сторінок для найшвидшого їх відтворення на пристроях користувачів.

Grafinės vartotojos sąsajos testavimas rankiniu būdu yra ilgai užtrunkantis procesas. Dėl šios priežasties sistema nėra ištestuojama pilnai ir atsiranda daug žmogiškųjų klaidų. Šiai problemai spręsti buvo suformuluoti uždaviniai, kurių tikslas yra automatiškai aptikti neteisingos kalbos ir lokalizacijos defektus mobiliosiose programėlės analizuojant jos resursus., Testing the graphical user interface manually is a time-consuming process. As a result, the system is not fully tested, and many human errors occur. To address this problem, tasks have been formulated to automatically detect incorrect language and localization defects in mobile applications by analyzing their resources.

Context: OpenStreetMap represents a collaborative effort of many different and unrelated users to create a free map of the world. Although contributors follow some general guidelines, unsupervised additions are prone to include erroneous information. Unfortunately, it is impossible to automatically detect most of these issues because there does not exist an oracle to evaluate whether the information is correct or not. Metamorphic testing has shown to be very useful in assessing the correctness of very heterogeneous artifacts when oracles are not available. Objective: The main goal of our work is to provide a (fully implemented) framework, based on metamorphic testing, that will support the analysis of the information provided in OpenStreetMap with the goal of detecting faulty information. Method: We defined a general metamorphic testing framework to deal with OpenStreetMap. We identified a set of good metamorphic relations. In order to have as much automation as possible, we paid special attention to the automatic selection of follow-up inputs because they are fundamental to diminish manual testing. In order to assess the usefulness of our framework, we applied it to analyze maps of four cities in different continents. The rationale is that we would be dealing with different problems created by different contributors. Results: We obtained experimental evidence that shows the potential value of our framework. The application of our framework to the analysis of the chosen cities revealed errors in all of them and in all the considered categories. Conclusion: The experiments showed the usefulness of our framework to identify potential issues in the information appearing in OpenStreetMap. Although our metamorphic relations are very helpful, future users of the framework might identify other relations to deal with specific situations not covered by our relations. Since we provide a general pattern to define metamorphic relations, it is relatively easy to extend the existing framework. In particular, since all our metamorphic relations are implemented and the code is freely available, users have a pattern to implement new relations.

Automatic testing of mobile applications has been a well-researched area in recent years. However, testing in industry is still a very manual practice, as research results have not been fully transferred and adopted. Considering mobile applications, manual testing has the additional burden of adequate testing posed by a large number of available devices and different configurations, as well as the maintenance and setup of such devices. In this paper, we propose and evaluate the use of a model-based test generation approach, where generated tests are executed on a set of cloud-hosted real mobile devices. By using a model-based approach we generate dynamic, less brittle, and implementation simple test cases. The test execution on multiple real devices with different configurations increase the confidence in the implementation of the system under test. Our evaluation shows that the used approach produces a high coverage of the parts of the application related to user interactions. Nevertheless, the inclusion of external services in test generation is required in order to additionally increase the coverage of the complete application. Furthermore, we present the lessons learned while transferring and implementing this approach in an industrial context and applying it to the real product.

Ankle sprains are common and often develop into chronic ankle instability. Ankle laxity is usually assessed by manual testing followed by magnetic resonance imaging to confirm the diagnosis. Manual testing however provides a subjective measure and is limited to the assessor sensibility. Current available technologies incorporate arthrometers to objectively measuring ankle laxity, but are not capable to assess the structural integrity of the capsuloligamentous structures. To overcome these limitations, we developed a novel medical device to assist in the diagnosis of ankle ligament injuries—the Porto Ankle Testing Device. With this device, it is possible to combine and correlate the assessment of the capsuloligamentous’ structural integrity with the joint functional competence (ie, joint multiplanar laxity). The main purpose of this work is to present the fundamental aspects and step-by-step development of the Porto Ankle Testing Device. We discuss the design specifications and technical requirements with the purpose to design and develop this medical device, described the features of the different components and explained the mechanical systems that are incorporated emulate manual testing and to measure the multiplanar ankle laxity. The preliminary findings are presented with the purpose to display the assessment protocol, the method of laxity measurement and the obtained results. We propose a unique and reliable medical device to safety and effectively assess ankle ligament injuries and contribute to enhance diagnosis, refine treatment indications and allow objective measurement of ligament laxity before and/or after stabilization surgery.

The detour test is a widely used test in comparative psychology that assesses various cognitive abilities, including inhibitory control. The goal of this study was to assess the degree of consistency in the performance of human children and capuchin monkeys on a manual detour test and on a computerized equivalent. Because computerized testing is more common in comparative research, it is important to determine whether a computerized version of the detour problem can provide measures of general inhibition that align with measures obtained from the same subjects when given a manual version. We found that human children and capuchin monkeys approached both tasks very differently and also that there was no correlation between the manual and the computerized task within each species. This suggests caution is needed when considering one format or the other when the goal is to use a single task to provide a general measure of inhibitory control.

Modern vehicles become increasingly digitalized with advanced information technology-based solutions like advanced driving assistance systems and vehicle-to-x communications. These systems are complex and interconnected. Rising complexity and increasing outside exposure has created a steadily rising demand for more cyber-secure systems. Thus, also standardization bodies and regulators issued standards and regulations to prescribe more secure development processes. This security, however, also has to be validated and verified. In order to keep pace with the need for more thorough, quicker and comparable testing, today's generally manual testing processes have to be structured and optimized. Based on existing and emerging standards for cybersecurity engineering, this paper therefore outlines a structured testing process for verifying and validating automotive cybersecurity, for which there is no standardized method so far. Despite presenting a commonly structured framework, the process is flexible in order to allow implementers to utilize their own, accustomed toolsets., 7 pages, 2 figures paper presented at IEEE VTC2021-Spring. Full published version at https://ieeexplore.ieee.org/document/9448913

In Software Development Life Cycle (SDLC), there are four phases involved. They are analysis, design, implement and testing. Testing is done to ensure the functionalities of the system are correct. There are many approaches to software testing. It is usually divided into two approaches: manual testing or automatic testing. However, these days, with the rapidly advanced technology, performing software testing manually has become hugely laborious but still doable. Therefore, experts of the software development field are beginning to go for automatic testing. This paper presents a case study of mobile application and discusses how test cases can be generated automatically from the application using different automatic tools. Three software testing tools have been used to generate test cases automatically. The results from generating test cases automatically from these three tools are then being compared together with the results of generating test cases using manual testing technique.

The Smart Driving Skill Evaluation (SDSE) System presented in this paper expedite the testing of candidates aspiring for a driving license in a more efficient and transparent manner, as compared to the present manual testing procedure existing in most parts of Asia and Pacific region. The manual test procedure is also subjected to multiple limitations like time consuming, costly and heavily controlled by the experience of examiner in conducting the test. This technological solution is developed by customizing 8051 controller based embedded system and LabVIEW based virtual instrument. The controller module senses the motion of the test vehicle on the test track referred to as zero rpm measurement and the LabVIEW based virtual instrument provides a Graphical User Interface for remote end monitoring of the sensors embedded on the test track. The proposed technological solution for the automation of existing manual test process enables the elimination of human intervention and improves the driving test accuracy while going paperless with Driving Skill Evaluation System. As a contribution to the society this technological solution can reduce the number of road accidents because most accidents results from lack of planning, anticipation and control which are highly dependent on driving skill., Comment: 19 pages

Dimensional quality control is a key issue in product manufacturing, particularly in long products such as rails or beams. To this end, international standards define precise methods to test if the dimensions are within the established tolerances, indicating whether they meet the required specification. The standards describe these methods using gauges that technicians can use to manually verify the dimensions of the product. In some cases, these methods provide different results from automated procedures, as they are based on different principles. To eliminate these discrepancies, this work proposes a novel automated method that emulates manual testing using virtual gauges. The proposed approach is based on an iterative procedure that aligns virtual gauges with the measured product shape, preventing one shape from penetrating another. This is achieved by assigning different weights to point correspondences according to their position. The result perfectly emulates the manual procedure, substituting the long and tedious manual procedure with a fast and robust automated alternative. Moreover, the proposed method can be applied to any dimensions with any type of gauge. Extensive tests with synthetic and manufactured rails corroborate the success of this approach.