Test Automation

Test Automation: How Programming Languages Rate

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.

Source: https://automationpanda.com/2017/01/21/the-best-programming-language-for-test-automation/


6 Best Practices with Integration Testing in CI Environments: TechBeacon


  • Integration first, until the fail
  • Then run Unit Tests to ID source
  • When Unit Tests pass again
  • Run Integration Tests
  • Bounce between the two until both are passing

TestAutomation: Initial Thoughts



Subscribe to Test Automation