How mega6453/appiumwizard works
Project Type and Purpose
• This is a monolithic, Windows desktop application built in .NET C# (Windows Forms) that orchestrates mobile‐automation testing.
• It bundles and manages Appium Server (via NodeJS), iOS/Android drivers, device proxies, screen reflection/control, profile management, IPA signing, and more—wrapping a host of external CLI tools in a single UI.
File Structure
• Top-level “Appium Wizard” folder: contains all UI forms (e.g., MainScreen, Server Settings, Object Spy) and core business logic (e.g., AndroidMethods.cs, iOSMethods.cs, Database.cs).
• “Resources”: embedded executables (adb, ffmpeg, iOS tools), data folder (appiumwizard.db), server packages (node.zip).
• Config files: NLog.config, app.manifest, .csproj.
• “Plugins Manager”: suggests a plugin-architecture extension point.
• Build/deployment: InnoSetup scripts under ExcludeInInstaller, CI workflows under .github/workflows.
README for Additional Insights
• Built-With stack: .NET C# WinForms, NodeJS, Appium (XCUITest, UIAutomator2), go-ios/pymobiledevice3/imobiledevice-net, adb, zsign, FFMpeg, Newtonsoft.Json, RestSharp.
• Core features: multi-server management, device addition, screen reflection, script execution, troubleshooting, plugins.
Main Components & Their Relationships
a. Frontend (Windows Forms UI)
• Screens/Forms (MainScreen, Server Settings, Plugins Manager, etc.)
• User actions → BLL calls
b. Business Logic Layer (.NET classes)
• Orchestrator services (AndroidMethods, iOSMethods, AppiumServerSetup, Database.cs)
• Plugin loader
c. Local Data Store
• SQLite file (appiumwizard.db) for storing device lists, server settings, profiles
d. Appium Server Processes
• NodeJS subprocesses managed by AppiumServerSetup (one per port)
• Default Capabilities & CLI args configured per server
e. External CLI Tools & SDKs
• Android: adb.exe, aapt(.exe/2), apksigner.jar, zipalign, ffmpeg for screen mirror
• iOS: go-ios tools (iproxy, plistutil, unzip, openssl, zsign, iOSServerPy.zip)
• pymobiledevice3/imobiledevice-net wrappers invoked from .NET
f. Plugins
• Dynamically installed node/npm modules or .NET assemblies managed via Plugins Manager
g. Automation Scripts (External)
• Clients connect to Appium server endpoints to drive device actions
Architectural Patterns & Design Principles
• Monolithic Desktop Orchestrator: single executable coordinating multiple subprocesses
• Facade/Adapter: .NET classes abstract complex CLI calls into simple methods
• Plugin Architecture: extension points for adding new functionality
• Layered Separation: UI → Orchestration layer → Data/storage + External tools
• Frontend (blue rectangle)
• BLL services (green rectangles)
• UI → BLL calls
• BLL → Database for CRUD
• BLL → NodeJS to start/stop servers
• BLL → CLI tools via shell calls
• External scripts → Appium Server (test execution)
c. Technologies on each component:
• “Windows Forms (.NET C#)” on UI
• “NodeJS Appium Server (npm)” on server processes
• “adb, ffmpeg, zsign, iproxy…” on External Tools