- Test Automation Patterns Wiki ( Dorothy Graham )
1. Update the Eclipse plugin.xml to a different "appName"
<?xml version="1.0" encoding="UTF-8"?> <?eclipse version="3.4"?> <plugin> <extension id="product" name="Java IDE" point="org.eclipse.core.runtime.products"> <product application="org.eclipse.ui.ide.workbench" name="Eclipse IDE"> <property name="preferenceCustomization" value="plugin_customization.ini"> </property> <property name="appName" value="Eclipse-410"> </property>
2. Create a new .desktop file & reference the "appName" for StartupWMClass
Was mulling over the C#/Java situation & couldn't find a compelling reason to use C# other than for WhiteBox Testing. It is slaved to M$ OS & ecosystem, meaning that any hardware used as a test fixture is going to have 40G of bloatware & 1000 background services running which doesn't seem efficient or advisable when consistent results are paramount.
Jumping on the web & AutomationPanda.com seems to come to the same conclusion - though has a preference of Python, probably due to it being a little more lightweight. I just can't get with the syntax/format marriage. I'm not a fan of formatting being a part of syntax. I suppose it forces some standardization of coding styles, but who says that standard is the best approach.
sudo yum install wget
# Install google-chromium
DOSBox on Pi
apt-get install dosbox
Copyright 2018· All rights reserved