ProcessNetteTester and WireHttp

[Guy Verville]

Hi,

I have some problem configuring a test with wireHttp involved.

This code works ok on a real template (called testPageController.php). I have two local sites to make the test.

	public function getOtherSiteConnectionTest() {
		$config = wire("config");
		$http = new WireHttp();
		$chemin = "http://" . $config->afmqOtherSite . "   /en/afmq-services/hello/";
		$response = $http->get($chemin);
		$expected = "hello";
		$actual = $response;
		Assert::equal($expected, $actual);
	}

Nette Tester tells me it has forgotten to make the test which means a misconfiguration of a sort. What I did wrong?

 

 

[tpr]

Could you post the entire test class (only with this one test method of course) to check?

[Guy Verville]

Sure! Of course, $path should be a valid path in your website.

<?php namespace ProcessWire;

use \Tester\Assert;
use \Tester\TestCase;

/**
 * @testCase
 */
class GetOtherSiteResponseTest extends TestCase {

	public function getOtherSiteConnectionTest() {
		$config = wire("config");
		$http = new WireHttp();
		$path = "http://" . $config->afmqOtherSite . "   /en/afmq-services/hello/";
		$response = $http->get($path);
		$expected = "Succès!";
		$actual = $response;
		Assert::equal($expected, $actual);
	}
}

(new GetOtherSiteResponseTest())->run();

The code of the template that responds is simple (this is crude test. I am using Twig templating).

<?php namespace ProcessWire;

require_once "MainController.php";

/**
 * Class AfmqServicesController
 * @package ProcessWire
 */
Class AfmqServicesController extends MainController {

	/**
	 * Simple test
     *
	 * @return void
	 */
	public function render(): void {
		$view = wire("view");
		$input = wire('input');
		$urlSegment = $input->urlSegment1;
		switch($urlSegment){
			case "hello":
				echo "OK";
				exit();
				break;
			default:
				exit();
				break;
		}
	}

}

(new AfmqServicesController())->render();

 

[tpr]

I think the issue is that the method name format is "testSomething" though I haven't read about it in the docs. Once I renamed the method it worked fine.

[Guy Verville]

Thank you, it was the problem!

[tpr]

Great, at least it turned out somebody makes use of the module ?

[Guy Verville]

You bet, our Quality Assurance department was very happy to discover that! While a lot of website do not require unit testing, we try to implement those with our more complex websites.