ADUG Melbourne February 2025 meeting

Meetings
1

Hi Everyone,
The Melbourne ADUG February meeting is on Monday Night 17th.

This meeting is going to be both at the Men’s Shed, and on Zoom. Opening around 6:00pm for a 6:15 start.

Richard King will present at the MMS shed on Monday.

He is going to give us an overview of automated testing.

We get to give feedback on what we consider to be potentially the most interesting/useful topic(s) from the overview. Some of the chosen topics will be presented in more detail at our Symposium later in the year.

Thanks

1 Like
2

──────────
Geoffrey Smith is inviting you to a scheduled Zoom meeting.
Join Zoom Meeting

Meeting ID: 813 0136 8087
Passcode: 768563

3

On Monday night Richard King with Brian Watson gave a presentation
on automated testing.

Brian’s programs (mcadx in this case) integrate with various CAD programs. (and a number of
versions of each) In the demo shown on Monday, there were Solidworks, Inventor, and Allegro

From the Website.

Using MCADX for SolidWorks, users of both Cadence Allegro X Design
Platform and Cadence OrCAD X Design Platform can co-design products
between preferred PCB editor technology and Dassault SolidWorks.

ECAD-MCAD (Electronic and Mechanical Cad) co-design of products using
an encrypted and zipped file exchange with IDX as the underlying
basis for the data format.

A seamless flow between the electronic and mechanical world is
important for the success of your design. The availability of the new
MCAD/ECAD co-design solution - MCADX for SolidWorks - helps to bridge
this gap with co-design between the PCB editor and SolidWorks and
introduces the following capabilities to the Allegro X and OrCAD X
design platforms:

Some of what we saw

The testing scripts could fire up the CAD programs. (with the MCADX
integrations loaded)

And then perform various operation on them. (clicking buttons, etc)
for example get the mechanical program to send some changes acrosss
to the electrical, and then have the electrical program accept the
changes in one test, and reject the changes in another. And see if
the mechanical program then correctly rolls back the changes (when
rejected)

And log all of this, with many screenshots.
It had handlers for when things went wrong. Where somewhat unexpected
alert boxes popped up. (eg. License server not responding)

Scripting

The testing is using python.
Using Behave for the testing
Behave, behavior driven development, python style.
And Pywin Auto to drive the UI of the cad programs (including the mcadx plugins)
With Allure Logging to log it all.

The presentation went quite long, but was very interesting.

Sorry, I don’t remember quite what was decided as to which section the
detailed presentation for the symposium will be. But it will be good.

Thanks
Richard and Brian.

1 Like
4

Thanks Roger.

Attached are some notes I put together which will help those interested get started with installing the necessary bits and pieces.

Cheers Richard

ADUG talk 17 Feb 2025.pdf (161.3 KB)

2 Likes