---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Design considerations for prompting

# Design considerations for prompting {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Generate your desired test by following the guided principles of effective prompting.

* Clear and concise ATF prompts that describes test steps
* Consider the scope and capability of Test generation
  * Test generation is a Now Assist backed skill to create ATF tests
  * The tests are created in the application scope that you are currently on
  * Other types of functional or integration tests are out of Test generation scope
  * Test generation can't update or delete existing ATF tests
  {#tg-prompt-design-considerations__ul_xwf_x5p_sdc}
* Test generation supports the following
  * Forms: open/submit form, field validation/visibility, UI/Declarative Action and Modal button. Each form API supports workspace as formUI type, including service_operations_workspace and asset_workspace and cmdb_workspace.
  * Server operations: impersonation/create user, log message, record CRUD, replay request, search catalog item and check out shopping cart.
  * Email: generate, reply, send and validate inbound / outbound email
  * Application Navigator: navigate to module, menu/module visibility
  * Reporting: report visibility, dash board visibility and sharing
  * Service Catalog: open/order catalog item, add item to shopping cart, set/validate item quantity, submit order, validate quantity, price, and variable status
  {#tg-prompt-design-considerations__ul_cn5_txp_sdc}

{#tg-prompt-design-considerations__ul_btk_f5p_sdc}  
{#tg-prompt-design-considerations__table_o43_zss_12c__entry__3}

| Good and effective prompts | Bad and irrelevant prompts | Comparison description |
|-|-|-|
| Write a test to create a new user with name Bill McDermott and assign the "itil" role. Create a new incident record, update the short description to "my new test record" and then validate the record description. Update caller to Bill McDermott, impact and urgency categories to "2- Medium" and submit the record. Delete the record and create a log for the deletion. | I need a new user Bill McDermott to open a new record. Make sure its called my new test record. Update caller to user, impact and urgency categories to Med. Delete the record and create a log for the deletion. | The bad prompt is irrelevant and incomplete for the following reasons: * No user role defined * Insufficient definition around the new user. Its unclear if the new user is to be created or impersonated * Insufficient definition around record handling with the name * No specific info about the caller field update * Not specific about category value to be used {#tg-prompt-design-considerations__ul_gv2_qts_12c} |
| Write an ATF test, named 'incident record test', impersonate admin, create a new incident record, then update the record short description to 'test update field from example', delete the record, then log a message 'record deleted' | Create an ATF test for an admin to create an incident record. Make description test update field from example. Then delete the record | The bad prompt lacks the following: * Does not specify "create a new user" or "impersonate" for the model to understand * Unclear expectation around setting description name * Unclear where exactly the name for the description begins {#tg-prompt-design-considerations__ul_tkw_k5s_12c} |
| Write a test to open Apple iPhone 13 catalog item, set color to 'pink', monthly data allowance to 500MB, validate price to be $800.00 and log the price | Write a test to open iPhone, color should be pink and data should be 500. The price should be 800. Log the price | The bad prompt is incomplete for the following reasons: * Catalog Item entity hasn't been called out * Missing keywords such as set or update for field value settings * Incomplete field id specified for monthly data allowance * Unclear expectation for price validation * Missing $ sign in price {#tg-prompt-design-considerations__ul_uxr_y5s_12c} |
[Tabela 1. Good vs. Bad prompt comparison]

{#tg-prompt-design-considerations__table_o43_zss_12c}
**Conceitos relacionados**   

* [Test generation design considerations](https://servicenow-prod.fluidtopics.net/dbpc1xhjMeYj4l3n5qPa2A "Leverage the full potential of Test generation by following these design considerations.")