Best Python code snippet using molecule_python
test_base.py
Source: test_base.py
...80 assert os.path.isdir(os.path.dirname(_instance._config.provisioner.inventory_file))81 assert os.path.isfile(_instance._config.config_file)82 _patched_manage_inventory.assert_called_once_with()83 _patched_write_config.assert_called_once_with()84def test_execute_cmdline_scenarios(85 config_instance, _patched_print_matrix, _patched_execute_scenario86):87 # Ensure execute_cmdline_scenarios runs normally:88 # - scenarios.print_matrix is called, which also indicates Scenarios89 # was instantiated correctly90 # - execute_scenario is called once, indicating the function correctly91 # loops over Scenarios.92 scenario_name = None93 args = {}94 command_args = {"destroy": "always", "subcommand": "test"}95 base.execute_cmdline_scenarios(scenario_name, args, command_args)96 assert _patched_print_matrix.called_once_with()97 assert _patched_execute_scenario.call_count == 198def test_execute_cmdline_scenarios_prune(99 config_instance, _patched_prune, _patched_execute_subcommand100):101 # Subcommands should be executed and prune *should* run when102 # destroy is 'always'103 scenario_name = "default"104 args = {}105 command_args = {"destroy": "always", "subcommand": "test"}106 base.execute_cmdline_scenarios(scenario_name, args, command_args)107 assert _patched_execute_subcommand.called108 assert _patched_prune.called109def test_execute_cmdline_scenarios_no_prune(110 config_instance, _patched_prune, _patched_execute_subcommand111):112 # Subcommands should be executed but prune *should not* run when113 # destroy is 'never'114 scenario_name = "default"115 args = {}116 command_args = {"destroy": "never", "subcommand": "test"}117 base.execute_cmdline_scenarios(scenario_name, args, command_args)118 assert _patched_execute_subcommand.called119 assert not _patched_prune.called120def test_execute_cmdline_scenarios_exit_destroy(121 config_instance,122 _patched_execute_scenario,123 _patched_prune,124 _patched_execute_subcommand,125 _patched_sysexit,126):127 # Ensure execute_cmdline_scenarios handles errors correctly when 'destroy'128 # is 'always':129 # - cleanup and destroy subcommands are run when execute_scenario130 # raises SystemExit131 # - scenario is pruned132 scenario_name = "default"133 args = {}134 command_args = {"destroy": "always", "subcommand": "test"}135 _patched_execute_scenario.side_effect = SystemExit()136 base.execute_cmdline_scenarios(scenario_name, args, command_args)137 assert _patched_execute_subcommand.call_count == 2138 # pull out the second positional call argument for each call,139 # which is the called subcommand. 'cleanup' and 'destroy' should be called.140 assert _patched_execute_subcommand.call_args_list[0][0][1] == "cleanup"141 assert _patched_execute_subcommand.call_args_list[1][0][1] == "destroy"142 assert _patched_prune.called143 assert _patched_sysexit.called144def test_execute_cmdline_scenarios_exit_nodestroy(145 config_instance, _patched_execute_scenario, _patched_prune, _patched_sysexit146):147 # Ensure execute_cmdline_scenarios handles errors correctly when 'destroy'148 # is 'always':149 # - destroy subcommand is not run when execute_scenario raises SystemExit150 # - scenario is not pruned151 # - caught SystemExit is reraised152 scenario_name = "default"153 args = {}154 command_args = {"destroy": "never", "subcommand": "test"}155 _patched_execute_scenario.side_effect = SystemExit()156 # Catch the expected SystemExit reraise157 with pytest.raises(SystemExit):158 base.execute_cmdline_scenarios(scenario_name, args, command_args)159 assert _patched_execute_scenario.called160 assert not _patched_prune.called161 assert not _patched_sysexit.called162def test_execute_subcommand(config_instance):163 # scenario's config.action is mutated in-place for every sequence action,164 # so make sure that is currently set to the executed action165 assert config_instance.action != "list"166 assert base.execute_subcommand(config_instance, "list")167 assert config_instance.action == "list"168def test_execute_scenario(mocker, _patched_execute_subcommand):169 # call a spoofed scenario with a sequence that does not include destroy:170 # - execute_subcommand should be called once for each sequence item171 # - prune should not be called, since the sequence has no destroy step172 scenario = mocker.Mock()...
Check out the latest blogs from LambdaTest on this topic:
People love to watch, read and interact with quality content — especially video content. Whether it is sports, news, TV shows, or videos captured on smartphones, people crave digital content. The emergence of OTT platforms has already shaped the way people consume content. Viewers can now enjoy their favorite shows whenever they want rather than at pre-set times. Thus, the OTT platform’s concept of viewing anything, anytime, anywhere has hit the right chord.
When working on web automation with Selenium, I encountered scenarios where I needed to refresh pages from time to time. When does this happen? One scenario is that I needed to refresh the page to check that the data I expected to see was still available even after refreshing. Another possibility is to clear form data without going through each input individually.
Most test automation tools just do test execution automation. Without test design involved in the whole test automation process, the test cases remain ad hoc and detect only simple bugs. This solution is just automation without real testing. In addition, test execution automation is very inefficient.
I was once asked at a testing summit, “How do you manage a QA team using scrum?” After some consideration, I realized it would make a good article, so here I am. Understand that the idea behind developing software in a scrum environment is for development teams to self-organize.
Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.
You could also refer to video tutorials over LambdaTest YouTube channel to get step by step demonstration from industry experts.
Get 100 minutes of automation test minutes FREE!!