Greg gregarendse

Testing An Angular CLI Project in a Headless Environment

I recently started a new project and we used [Angular CLI][4] to get started. Angular CLI, as in the name, is a command line utility for creating and managing Angular 2 projects. Using Angular CLI to create a project is very easy and it gives you a great starting point for new Angular 2 projects. The only draw back I found was that in my mind it wasn't CI ready.

Angular CLI out of the box gives you a few unit tests and an end to end (e2e) test. This is great because you can generate a project and set up your build server to build the artefacts. This is where I ran into problems.

Having everything generated for you is great until something you want to do does not work; and this is where I was. I wanted to build and test my angular application on a headless build agent. The generated code from Angular CLI runs tests using Google Chrome by default. Which is fine, but running Google Chrome on a bui

	#!/usr/bin/env python3
	"""
	DNSmasq to MikroTik DNS Static Converter

	Converts dnsmasq server configurations to MikroTik RouterOS DNS static entries.
	Supports various dnsmasq directive formats and generates appropriate MikroTik commands.
	"""

	import re
	import sys

	#!/bin/bash

	# settings
	# Login information of freenom.com
	freenom_email="main@address"
	freenom_passwd="pswd"
	# Open DNS management page in your browser.
	# URL vs settings:
	# https://my.freenom.com/clientarea.php?managedns={freenom_domain_name}&domainid={freenom_domain_id}
	freenom_domain_name="domain.name"