{
	"id": "110236",
	"key": "ALOY-538",
	"fields": {
		"issuetype": {
			"id": "4",
			"description": "An improvement or enhancement to an existing feature or task.",
			"name": "Improvement",
			"subtask": false
		},
		"project": {
			"id": "11113",
			"key": "ALOY",
			"name": "Alloy",
			"projectCategory": {
				"id": "10400",
				"description": "Tools for developing applications",
				"name": "Tooling"
			}
		},
		"fixVersions": [],
		"resolution": null,
		"resolutiondate": null,
		"created": "2013-02-26T15:06:25.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [
			"notable"
		],
		"versions": [
			{
				"id": "15271",
				"description": "Alloy 1.1.0, concurrent with SDK 3.1.0",
				"name": "Alloy 1.1.0",
				"archived": false,
				"released": true,
				"releaseDate": "2013-04-16"
			}
		],
		"issuelinks": [],
		"assignee": null,
		"updated": "2018-03-07T22:26:09.000+0000",
		"status": {
			"description": "The issue is open and ready for the assignee to start work on it.",
			"name": "Open",
			"id": "1",
			"statusCategory": {
				"id": 2,
				"key": "new",
				"colorName": "blue-gray",
				"name": "To Do"
			}
		},
		"components": [
			{
				"id": "13604",
				"name": "Tooling",
				"description": "Items related to Alloy tooling and workflow"
			}
		],
		"description": "h2. description\r\n\r\n\"jake\" is included in the package.json as a dependency of Alloy. While jake is used to run the test scripts, it needs to be installed as \"sudo npm install -g jake\". The \"jake\" module that is local to the alloy installation is never actually used and should thus be removed from the dependency listing.\r\n\r\nWe should instead include the \"devDependencies\" key in the package.json which would include jake and a few others. To make it easy for developers to access jake, which would then be buried alloy's global location's node_modules folder, something like this on mac:\r\n\r\n{code}\r\n/usr/local/lib/node_modules/alloy/node_modules/.bin/jake\r\n{code}\r\n\r\nWe should create an \"alloy test\" command that can do what the jake calls were able to do. This will make it easier and allow us to give a uniform interface for testing and running test apps.\r\n\r\nh2. proposed syntax\r\n\r\nh4. run all tests\r\n\r\n{code}\r\nalloy test \r\n\r\n# or\r\n\r\nalloy test --spec all\r\n\r\n# or just\r\n\r\nnpm test\r\n{code}\r\n\r\nh4. run specific test by spec name\r\n\r\n{code}\r\nalloy test --spec SPEC_NAME\r\n\r\n# ex. alloy test --spec compile\r\n{code}\r\n\r\nh4. run test app\r\n\r\n{code}\r\nalloy test --testapp TEST_APP_DIR [options]\r\n\r\n# ex. alloy test --app models/todo\r\n# ex. alloy test --app ui/tabbedbar --platform ios\r\n# ex. alloy test --app ui/android_menu --platform android\r\n{code}",
		"attachment": [],
		"flagged": false,
		"summary": "Create \"alloy test\" command",
		"creator": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"subtasks": [],
		"reporter": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"environment": null,
		"comment": {
			"comments": [],
			"maxResults": 0,
			"total": 0,
			"startAt": 0
		}
	}
}