![]() Integrates these web services APIs, translates data to presentation, andĭelivers to mobile devices for rendering. Security trading-sit in application servers, and a content gateway System, financial services-such as account management, bill payment, To contemporary applications, the Web has become a fundamental layer Objectives: Show the audience how you can use the change impact analysis technique to detect the subset of test cases affected by a change on the source code. Should be retested after the transformation.Īudience: Erlang developers and researchers Research focuses on selecting test cases affected by refactorings that Most expensive part of the lifecycle of software systems, so our Refactorings should preserve the original behaviour of the system,ĭevelopers want to be convinced about that, thus they retest the Programmer or using a refactoring tool, such as RefactorErl. The change can be performed manually by the Is we want to measure the impact of any change made on the source code:Įspecially we want to select a subset of test cases which must be rerunĪfter the modification. Our goal is to perform change impactĪnalysis of Erlang programs based on the resulted program slices, that The server is restarted again.Program slicing is a well-known technique that utilizes dependency In the end_per_suite previously backuped config file is restored and The expected certificate files exists and then produces new config file.Īt the end it restart the server so that the new configuration can be applied. The above snippet backups current server's config file, asserts that Make_ejabberd_node_require_starttls( Config) -> ejabberd_node_utils: modify_config_file(, Restore_ejabberd_node( Config) -> ejabberd_node_utils: restore_config_file( Config),Įjabberd_node_utils: restart_application( ejabberd).Īssert_cert_file_exists() -> ejabberd_node_utils: file_exists( ? CERT_FILE) orelse ct: fail( "cert file ~s not exists ", ). ![]() ![]() Make_ejabberd_node_require_starttls( Config1),Įjabberd_node_utils: restart_application( ejabberd), Setup_ejabberd_node( Config0) -> Config1 = ejabberd_node_utils: init( Config0),Įjabberd_node_utils: backup_config_file( Config1), Init_per_suite( Config) -> setup_ejabberd_node( Config).Įnd_per_suite( Config) -> restore_ejabberd_node( Config). In order to do this define configuration variables in nfig file, for example: ![]() It is possible to run tests for various ejabberd configurations. Make quicktest TESTSPEC=custom.spec ADD_OPTS="-pa /full/path/to/erlcloud/ebin" Testing various server configurations Of course TESTSPEC and ADD_OPTS can be specified at the same time: Make quicktest ADD_OPTS="-pa /full/path/to/erlcloud/ebin" spec file (for example to add other suites or remove the existing ones) one must add it to one of the mentioned commands:Īdditional erlang binaries required by custom suites can be added to the path by providing ADD_OPTS parameter to the make command. ![]() full ( make test) - this command tests all server configurations defined in nfig file - see the section on various server configurationsīy default both commands are using the default.spec file where options like suites to run, config file(s) and log dir are specified.quick ( make quicktest) - this command tests the current configuration of the server.It's used mainly for ESL's branch of ejabberd,īut one that may be reused in other projects. This repository contains test code for ejabberd/MongooseIM. ![]()
0 Comments
Leave a Reply. |