-
Syllabus
-
Terminology
- Introduction into MDBCore testing
-
Introduction - Agenda 2 min
-
Hardware and Software for Demo 1 min
- Why FW Test Automation?
-
Motivation 3 min
-
Firmware Testing with MPLAB® X 1 min
- MDBCore & MPLABX ecosystem
-
Architecture 2 min
-
MDBCore use-cases 5 min
-
MPLAB® X SDK 2 min
- Summary
-
Summary 2 min
-
Please provide some feedback!
Automate FW testing with MDBCore scripting - Introduction
This course introduces the potential of MDBCore-scripting in automating firmware testing. (December 2023)
The objective of this series of courses is to showcase the potential of MDBCore-scripting in automating firmware testing.
Target audience: FW-tester, Quality or Project-Leads
Knowledge: working experience of MPLAB®X & any OO-language knowledge helpful
1)Introduction Course: We commence by exploring the MPLABX ecosystem, the MDBCore, and the SDK, before delving into specific use-cases.
2)Compile without IDE: Prior to firmware testing, we examine the process of automatically compiling sources into *.elf files from a script.
We are now prepared to explore the three distinct MDBCore usage models for automated firmware testing.
3.a) MDBCore Interface mdb: The MDB, as the simplest and first method to utilize MDBCore, includes a script mdb.bat/.sh that manages instructions from an mdb-commands.txt file. However, it has certain limitations that are addressed with the next usage model, mdbcs.
3.b) MDBCore Interface mdbcs: mdbcs is designed to overcome the limitations of mdb. It is delivered as a Java module, mdbcs.jar, thus requiring a scripting language with a Java interface, such as Jython. This adds a bit more complexity but resolves the mdb limitations and provides access to a wide range of Java libraries, such as the Java Swing library for simplified user interfaces.
3.c)FW test automation with Java: The final and most complex usage model is pure Java, which offers full MDBCore functionality, albeit with the highest level of complexity.