Blog Tag

This blog seeks to inform test code creators and test automation practitioners about real-world best practices for using and integrating open source software. Many of the missteps described also apply to code published under proprietary / closed-source licenses, albeit with different terms and particulars. It is not intended to scare readers away from open source but rather, to inform test automation practitioners how to avoid the most common missteps, to realize the greatest value from open source software with the least risk.

Open source is a methodology whereby developers collaborate to create and share software, documentation and other artifacts.. Inner source is the application of the same methods but within a single organization. It applies to test automation as it does to other types of software, fostering collaboration, transparency, and shared ownership of testing tools and frameworks.

An OSPO or Open Source Program Office is a centralized team or department within an organization that manages open source strategy, policies, and practices. The concept of an OSPO has become increasingly popular as more companies recognize the importance of open source in software development and IT in general.