AMS 4.2 Section 2.3.2

Content-Run-As-Service is an attribute when set to YES, defaults the following MVM attributes to YES:
Sprint-Launch-Power-On, Sprint-No-Exit, Sprint-Background-No-Pause and Sprint-Launch-Background.

If one of those attributes is defined and set to NO then the default of YES is overwritten

---

CRAS_test1 has the following attributes:
Content-Run-As-Service: yes

---

CRAS_test2 has the following attributes:
Content-Run-As-Service: invalid
App MUST ignore the Content-Run-As-Service attribute and not launch the app on PowerOn.

---

CRAS_test3 has the following attributes:
Content-Run-As-Service: yes
Sprint-Launch-Background: no
App MUST launch to the Foreground on PowerOn and Application MUST not be allowed to Exit.

---

CRAS_test4 has the following attributes:
Content-Run-As-Service: yes
But the app is UNSIGNED
App MUST ignore the Content-Run-As-Service attribute and not launch the app on PowerOn.

---

CRAS_test5 does not have the Content-Run-As-Service attribute
App MUST ignore the Content-Run-As-Service attribute and not launch the app on PowerOn.

---

CRAS_test6 has the following attributes:
Content-Run-As-Service: yes
App MUST launch to Background on Power On and Application MUST not be allowed to Exit.

---

CRAS_test7 has the following attributes:
Content-Run-As-Service: yes
Sprint-Launch-Power-On: no
App MUST launch to Background and continue to run, but NOT on PowerOn.

---

CRAS_test8 has the following attributes:
Content-Run-As-Service: yes
Sprint-No-Exit: no App MUST launch to the background on Power On, continue to run and be allowed to exit.

---

CRAS_test9 has the following attributes:
Content-Run-As-Service: yes (JAD only)
TBD.

---

These tests are only applicable for devices that support a Multitasking Virtual Machine.