Serena Gray's Blog

What is Unit Testing? This is a type of testing which is done by software developers in which the smallest testable module of an application - such as functions, interfaces, or procedures - are tested to ascertain if they're fit to use. The objective of unit testing is to split each portion of the source code and also check that each part works properly. This ought to mean that if any group of input is fed to function or procedure, it should return an expected output. Advantages of unit testing : Defects are observed at an early stage. As it is done by the dev group by testing individual pieces of code prior to integration, it assists in fixing the issues early on in source code without impacting other source codes. It will help maintain the code. As it's accomplished by individual programmers, stress is being put on making the code interdependent, which then reduces the chances of impacting other sets of source code.  It aids in cutting the cost of defect fixes because bugs ar

Each IoT tool has its hardware and relies on software to drive it. As there are so many variants of hardware and software for devices, as well as different versions of firmware and operating systems, it may be impossible to test all probable combinations of hardware and applications. To specify a reasonable subset that may be examined efficiently, collect information from your end-users to understand which devices and software versions they're using, and analyse it to ascertain the most popular mixes. As soon as you know which devices and operating systems to check, you can concentrate the majority of your testing on these mixes, and run smaller sanity tests on less common combinations. IoT devices now use many distinct communication protocols to interact with controls, and with every other. Protocols such as Message Queuing Telemetry Transport (MQTT), Extensible Messaging and Presence Protocol (XMPP), and Constrained Application Protocol (CoAP) are typical, and each has its advant

Regression Testing  of an already tested program, after modification, to detect any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software components. In simple words, We do regression by re-executing the tests against the modified program to evaluate whether the altered code breaks anything that was working earlier. Anytime we do alter an application, we should do regression testing (we run regression test). Regression testing provides confidence to the programmers that there's no broken functionality after changing the manufacturing code. It makes sure there are not any unexpected side effects. Hope you've understood what's regression tests. Now let us see when can we do this kind of analysis. Regression Testing Example Assume there is an application that has a performance to insert', 'Save', and delete'. These functions make it possible for users to add data, save data, and delet