# Usa Chromium invece di Chrome per la suite di test

**URL:** https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772
**Category:** Development
**Created:** [27 Agosto 2018, 7:33pm UTC](https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772 "2018-08-27T19:33:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![sudoman](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@sudoman](https://meta.discourse.org/u/sudoman)
#### Post date: [27 Agosto 2018, 7:33pm UTC](https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772/1 "2018-08-27T19:33:57Z")

</div>

Hello Discourse team,

I noticed that your `image/discourse_test/Dockerfile` file installs Google Chrome. It would be great if you use Chromium instead, because it is free software and is virtually the same as Google Chrome, except for the lack of Flash and H.264 decoding features. The version of Chromium in Ubuntu’s repos is as recent as Google’s upstream version and I suspect that you don’t need any of the proprietary features.

Could you please use Chromium instead? It’s great to see that Discourse is free software, but it’s a downer that your testing suite is using proprietary software. I don’t want to run the tests I was planning working on because of this non-free package.

Running this on Xenial:

```plaintext
$ apt-cache policy chromium-browser
chromium-browser:
  Installed: (none)
  Candidate: 68.0.3440.75-0ubuntu0.16.04.1
  Version table:
     68.0.3440.75-0ubuntu0.16.04.1 500
        500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
        500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
     49.0.2623.108-0ubuntu1.1233 500
        500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

```

Thanks,  
Andrew

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [27 Agosto 2018, 9:06pm UTC](https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772/3 "2018-08-27T21:06:29Z")

</div>

We do use Chrome and some related libraries for tests, like [GitHub - GoogleChrome/chrome-launcher: Launch Google Chrome with ease from node. · GitHub](https://github.com/GoogleChrome/chrome-launcher).

I don’t think we have the bandwidth to tackle this problem anytime soon, so would you like to work on a PR that makes our test system chromium compatible ?

---

<div class="post-metadata">

### Author: ![Daan\_Seegers](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/daan_seegers/32/99611_2.png) [@Daan\_Seegers](https://meta.discourse.org/u/Daan_Seegers)
#### Post date: [27 Agosto 2018, 11:23pm UTC](https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772/4 "2018-08-27T23:23:31Z")

</div>

I do not use discourse that much. Why is chrome used for?

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [28 Agosto 2018, 1:08am UTC](https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772/5 "2018-08-28T01:08:10Z")

</div>

> [@Daan\_Seegers](#):
>
> Why is chrome used for?

Chrome headless is used to run our client side test suite.

---

<div class="post-metadata">

### Author: ![sudoman](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@sudoman](https://meta.discourse.org/u/sudoman)
#### Post date: [29 Agosto 2018, 4:04pm UTC](https://meta.discourse.org/t/please-use-chromium-instead-of-chrome-for-testing-suite/95772/6 "2018-08-29T16:04:01Z")

</div>

Hello Rafael,

Unfortunately I don’t have much bandwidth either. In case anyone is interested in working on this in the future, it looks like it’s possible to set the `chromePath` variable when calling `chrome-launcher`. Perhaps it could be set to point to the Chromium browser.

Thanks,  
Andrew