MakerMate

What is MQTT?
MQTT (MQ Telemetry Transport) is a lightweight open messaging protocol that provides resource-constrained network clients with a simple way to distribute telemetry information in low-bandwidth environments. The protocol, which employs a publish/subscribe communication pattern, is used for machine-to-machine (M2M) communication.

What is QoS?
Quality of Service (QoS) in MQTT messaging is an agreement between sender and receiver on the guarantee of delivering a message. There are three levels of QoS :

• 0 - at most once
• 1 - at least once
• 2- exactly once

When a client (e.g. a remote IoT device) is publishing to a broker, the client determines the QoS level for that message. When the broker sends the message to a subscribing client, the QoS set by the first client for that message is used again.So effectively the original publisher of any message determines the QoS of the message all the way to the final recipients.

QoS is a key feature of the MQTT protocol. QoS gives the client the power to choose a level of service that matches its network reliability and application logic. Because MQTT manages the re-transmission of messages and guarantees delivery (even when the underlying transport is not reliable), QoS makes communication in unreliable networks a lot easier.

For our application we need to receive all messages exactly once and the duplicate delivery can harm the functioning of application. Therefore, we used QoS = 2, as it is the highest level of service in MQTT and it ensure the property that messages are received only once by the intended recipients. Eventhough it is the safest, QoS 2 interaction takes more time to complete. The guarantee is provided by at least two request/response flows (a four-part handshake) between the sender and the receiver. The sender and receiver use the packet identifier of the original PUBLISH message to coordinate delivery of the message.

Therefore, with the integration of HTTPS and MQTT the functioning of Information Console was implemented.

The software testing of our product required, basically two steps,

• Authentication Testing
• Functionality Testing

In testing the functioning of our product, we need to test both the Information console and Inventory Management system. This will ensure the proper functioning of them and it helps us to fix the errors.

Tools and Softwares used in testing

• 

This is an application used for API testing. In our application we used it in testing the API calls that required for functioning of Mobile app and Information Console. It was easy to tests HTTP requests, as it is with a graphical user interface, through which we obtain different types of responses that need to be subsequently validated. It also offers many endpoint interaction methods(GET, POST, PUT, DELETE) and it has the possibility to create different testing environments that made our work easy. Futher, it helps us optimize our time when executing tests.



• 

Laravel Unit-Testing

In Laravel, there are two ways to test your application. One is with Unit testing while other is with Feature testing. Unit testing allows us to test classes models, controllers etc, while Feature testing enables to test the code base. This testing ensures that each and every component of the application passes from the standard testing process and application doesn’t go broken for deployment. Also this is really fast and easy to handle.