Bruno P. Kinoshita kinow

When you are working on a project, you normally know what code needs testing. For this example I will show a way to figure out what is missing tests. Just keep in mind that not all of your code needs or can be tested (e.g. in Java OutOfMemoryError or IOException blocks can be tricky to test).

Code Coverage

When running your code with tests, some tools keep track of what portion of the code was actually executed with the tests.

Memory heap allocation

Tested with production mode and development mode, and in both cases the memory appeared to be going up in five, which is not a good sign.

Left it running for 30 minutes whilst I collected the memory heap for analysis in the browser.

33.9% of the memory was in client.onmessage. That's the part of GraphQL Apollo client that receives the messages from the server. 22.14% of the total is in Vuex SET for the GScan workflows data (it appears under client.onmessage due to the tree call, as SET is called after the data is received

Environment

Thinkpad T530 16GB 8cores. Ubuntu LTS 18.04 up to date. Anaconda Python 3.7.7, with a venv virtual environment activated.

Latest branches of cylc-flow (9d60d6858113322f607b408fb3ead34b3f98a142) and cylc-uiserver (0eba8f3af77ed3adfb10a2f6510b247beaa1fcdc).

Chromium 84. As Cylc UI was built for production mode, VueDevTools doesn't interfere with the performance tests, as it won't be activated either during the tests. I will use only the browser default development tools and lighthouse. Also disabled uBlock origin for localhost.

See file suite.rc for complex workflow source.

	Found conflicts! Looking for incompatible packages.
	This can take several minutes. Press CTRL-C to abort.
	failed

	Leaving build/test directories:
	Work:
	/home/kinow/Development/python/miniconda3/envs/test/conda-bld/work
	Test:
	/home/kinow/Development/python/miniconda3/envs/test/conda-bld/test_tmp
	Leaving build/test environments:

	subscription OnWorkflowDeltasData($workflowId: ID) {
	deltas(workflows: [$workflowId], stripNull: true) {
	...WorkflowTreeDeltas
	__typename
	}
	}

	fragment WorkflowTreeDeltas on Deltas {
	id
	shutdown

	{
	"id": "2",
	"type": "data",
	"payload": {
	"data": {
	"deltas": {
	"id": "kinow\|five",
	"shutdown": false,
	"added": {
	"workflow": {

	[scheduling]
	initial cycle point = 19831213T0600Z
	final cycle point = 19831213T0700Z

	[[dependencies]]
	[[[R1]]]
	graph = "test"

	[runtime]
	[[test]]

	{
	"data": {
	"workflows": [
	{
	"id": "kinow\|messagetrigger1",
	"tasks": [
	{
	"id": "kinow\|messagetrigger1\|bar",
	"proxies": [
	{

	from datetime import datetime
	from airflow import DAG
	from airflow.operators.dummy_operator import DummyOperator
	from airflow.operators.python_operator import PythonOperator

	def print_hello():
	return 'Hello world!'

	# schedule_interval supports CRON syntax
	dag = DAG('hello_world', description='Simple tutorial DAG',