Puppet Labs vs Selenium: What are the differences?
Developers describe Puppet Labs as "Server automation framework and application". Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification. On the other hand, Selenium is detailed as "Web Browser Automation". Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that. Boring web-based administration tasks can (and should!) also be automated as well.
Puppet Labs belongs to "Server Configuration and Automation" category of the tech stack, while Selenium can be primarily classified under "Browser Testing".
"Devops" is the primary reason why developers consider Puppet Labs over the competitors, whereas "Automates browsers" was stated as the key factor in picking Selenium.
Puppet Labs and Selenium are both open source tools. Selenium with 14.7K GitHub stars and 4.92K forks on GitHub appears to be more popular than Puppet Labs with 5.34K GitHub stars and 2.1K GitHub forks.
According to the StackShare community, Selenium has a broader approval, being mentioned in 770 company stacks & 425 developers stacks; compared to Puppet Labs, which is listed in 181 company stacks and 48 developer stacks.
What is Puppet Labs?
What is Selenium?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Selenium?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I'm using puppet to configure my servers. This makes it really simple to ensure that I have the same environment. There is a bit of a learning curve, but the repeatability definitely makes it worth the effort. I found puppet to be a little easier to pick up relative to chef, but I've used both. They're both great solutions.
I really like that there are a lot of modules available on the puppet forge that are being actively maintained.
We provision all servers with puppet. We have one central Puppet server which uses puppet modules referenced by a Puppetfile. Those puppet modules are partly from forge and partly self written.
All modules which are self written, have to be tested using rspec-puppet and beaker.
가장 강력한 웹 UI / UX 테스트 툴 이지만, 문제도 많다. iframe 안에 있는 건 잘 select 가 안되기도 하고, 화면이 작아 컴포넌트가 화면에 보이지 않으면 또 select 할 수 없다. 하지만 브라우저를 있는 그대로 제어 할 수 있다는 게 가장 큰 매력이다.
ps. selenide 와 같이 쓰면 코드가 많이 개선된다.
Maintaining and expanding automated regression tests is one of my primary responsibilities at CrowdTwist. We use Selenium to test the front-end parts of our platform.
Opstax uses puppet for role/profile based configuration management and the distribution of small/static code.
Used Selenium web-driver for automated QA testing in continuous integration and continuous deployment.
- Navigating our site for tests
- Navigating other sites that discriminate against non-human visitors
Configures or servers and allows us to be region independent we have 5 regions across the globe.
Selenium is a great way to automatically test if a build is sane and can be deployed.