Show TOC

Step 3: Adding the Price FormatterLocate this document in the navigation structure

We will now take care of the implementation of the price formatter and make sure that the tests we wrote in the previous step run successfully.

If the tests are passed, we can be sure that the formatter is formally correct but it is still not visible in the app. So additionally, we will add the formatter to the UI to be able to verify and check that the price is shown properly.

Figure 1: The price is now formatted with a semantic color

You can view and download all files in the Explored app in the Demo Kit under Testing - Step 3 .

], function (Text) {
	"use strict";
	return {
		numberUnit: function (sValue) {
		 * Defines a value state based on the price
		 * @public
		 * @param {number} iPrice the price of a post
		 * @returns {string} sValue the state for the price
		priceState: function (iPrice) {
			if (iPrice < 50) {
				return "Success";
			} else if (iPrice >= 50 && iPrice < 250) {
				return "None";
			} else if (iPrice >= 250 && iPrice < 2000) {
				return "Warning";
			} else {
				return "Error";

We change the empty formatter function that we have added in the last step and add the implementation details to it. If the implementation matches the specification embedded in our tests we are done with implementing the formatter.

The input for the formatter is the price value from the model and the result is the state as a string value. The actual implementation logic is quite simple and returns a semantic state value based on the price as we have seen already in the test. There are four cases that are reflected in the if/else statements inside the formatter.

You can now run the file webapp/test/unit/unitTests.qunit.html and check if the unit tests run successfully. You should see your new test cases on the result page. If the overall result is successful then we have successfully implemented our first feature.

<ColumnListItem vAlign="Middle">
				path: 'Price',
				formatter: '.formatter.numberUnit'
				path: 'Price',
				formatter: '.formatter.priceState'

We still have to apply the changes to our UI so that we can actually see the formatted price in the app. Unit tests are typically testing the logic independent of the user interface. That is why the tests are running successfully even though we did not adapt the UI yet.

In our worklist view we simply add a state attribute to the ObjectNumber control in the columns aggregation. We define the same data binding path as for the number, but we use our new formatter function to determine the proper state. If you now run the webapp/test/mockServer.html file, you can see that some of the product prices are listed in green, black, orange, and red depending on their price.