About Vipin JAin

In Family, Vipin is blessed to live with his Parents, a beautiful wife and two teens aged 20 and 18. His Wife has a PhD Computer Science and was a fellow speaker with him in few of his international conferences. Vipin’s Daughter is pursuing Designing and his Son is a budding author, having published two books on Amazon already.
In his job, Vipin was the first guy in his company to work on automation way back in 2004. Automation is everywhere now! He worked on SilkTest at that time for functional testing automation.
Vipin’s speaking profile started in 2012 and he feels lucky enough to have spoken across Europe, at least once every year since 2012. At Testing United, this would be his third conference in a row since 2019. Other Key conferences include QA&Test, Bilbao Spain in 2012, 2016 and 2018, 2020, QATest Security conference Madrid 2021, ExpoQA Madrid 2015, TestingCup 2017, Belgrade Testing Conference 2018, Poznan Meetups like PTaQ, WrotQA and Girls who Test in 2017 and 2018.
Fun fact: In his school, Vipin hated computers and wanted to be a Doctor. Then he never liked to be a QA and wanted to be a programmer. and here he is, 24 years in IT, 17 years in QA and spoken 17 times in international conferences. He believes in Destiny!

Speech title:

End to End testing solution to maintain IoT Ecosystem Integrity

About his speech:

The IoT solutions are evolving, hence a comprehensive thought process is required to test them. Although there exists known testing practices and activities , the density and the combination of technologies are changing. In the past, embedded software engineering was positioned apart from other areas of the software development landscape, but this is no longer the case, as the entire stack of applications can often function as a single solution. People in charge of system quality need to understand the challenges related to low-level embedded testing, as well as service components. The structure of IoT systems has evolved beyond simple client devices providing data or receiving instructions. Instead of simply performing actions based on instructions received from “the cloud,” IoT systems have powerful algorithms that make decisions based on data from within their subsystem. The idea that IoT components may be connected in complex configurations requires us to think about the exponentially expanding problem of testing IoT architectures. When you create applications that publish and/or consume services within an IoT environment, it is your responsibility to ensure that all elements of the solution stack function correctly. This usually includes low-level testing of the microcontroller layer, as well as higher-level verification of transactions between the various endpoints.  The wide array of technologies now being deployed in very basic solutions used to be characteristic of bigger, more expensive projects, such as logistic systems developed for large organizations, which often rely on homegrown solutions for testing. In the current IoT world, we need to ensure that the information is correctly exchanged and interpreted from end-to-end. Organizations should be equipped with easy-to-use and reliable testing solutions that are able to test such a broad array of technologies and help analyze testing results from different sub-components of the solution. Problem We were facing: How to ensure that the information travels correctly through the wide array of incompatible devices and protocols. Solution: We deconstruct the system in layers for effective testing at each layer. Small automation frameworks were constructed around them. Test plans were made to involve unit testing, integration and End to End testing. the overall approach was to use the module interface definition to build the test suites and automate the execution.

Takeaways:
1. IoT solution testing is different from normal testing as it comprises of layers and each layer may require a different type of testing.
2. Delivering a high-quality system requires testing capabilities at every layer
3. All well known testing techniques are considered for IoT testing as we need to test entire mesh like hardware, software and firmware.




About Vipin JAin

In Family, Vipin is blessed to live with his Parents, a beautiful wife and two teens aged 20 and 18. His Wife has a PhD Computer Science and was a fellow speaker with him in few of his international conferences. Vipin’s Daughter is pursuing Designing and his Son is a budding author, having published two books on Amazon already.
In his job, Vipin was the first guy in his company to work on automation way back in 2004. Automation is everywhere now! He worked on SilkTest at that time for functional testing automation.
Vipin’s speaking profile started in 2012 and he feels lucky enough to have spoken across Europe, at least once every year since 2012. At Testing United, this would be his third conference in a row since 2019. Other Key conferences include QA&Test, Bilbao Spain in 2012, 2016 and 2018, 2020, QATest Security conference Madrid 2021, ExpoQA Madrid 2015, TestingCup 2017, Belgrade Testing Conference 2018, Poznan Meetups like PTaQ, WrotQA and Girls who Test in 2017 and 2018.
Fun fact: In his school, Vipin hated computers and wanted to be a Doctor. Then he never liked to be a QA and wanted to be a programmer. and here he is, 24 years in IT, 17 years in QA and spoken 17 times in international conferences. He believes in Destiny!

Speech title:

End to End testing solution to maintain IoT Ecosystem Integrity

About his speech:

The IoT solutions are evolving, hence a comprehensive thought process is required to test them. Although there exists known testing practices and activities , the density and the combination of technologies are changing. In the past, embedded software engineering was positioned apart from other areas of the software development landscape, but this is no longer the case, as the entire stack of applications can often function as a single solution. People in charge of system quality need to understand the challenges related to low-level embedded testing, as well as service components. The structure of IoT systems has evolved beyond simple client devices providing data or receiving instructions. Instead of simply performing actions based on instructions received from “the cloud,” IoT systems have powerful algorithms that make decisions based on data from within their subsystem. The idea that IoT components may be connected in complex configurations requires us to think about the exponentially expanding problem of testing IoT architectures. When you create applications that publish and/or consume services within an IoT environment, it is your responsibility to ensure that all elements of the solution stack function correctly. This usually includes low-level testing of the microcontroller layer, as well as higher-level verification of transactions between the various endpoints.  The wide array of technologies now being deployed in very basic solutions used to be characteristic of bigger, more expensive projects, such as logistic systems developed for large organizations, which often rely on homegrown solutions for testing. In the current IoT world, we need to ensure that the information is correctly exchanged and interpreted from end-to-end. Organizations should be equipped with easy-to-use and reliable testing solutions that are able to test such a broad array of technologies and help analyze testing results from different sub-components of the solution. Problem We were facing: How to ensure that the information travels correctly through the wide array of incompatible devices and protocols. Solution: We deconstruct the system in layers for effective testing at each layer. Small automation frameworks were constructed around them. Test plans were made to involve unit testing, integration and End to End testing. the overall approach was to use the module interface definition to build the test suites and automate the execution.
Takeaways:
1. IoT solution testing is different from normal testing as it comprises of layers and each layer may require a different type of testing.
2. Delivering a high-quality system requires testing capabilities at every layer
3. All well known testing techniques are considered for IoT testing as we need to test entire mesh like hardware, software and firmware.