What the heck does [...] mean in your documenation?

How to apply eValid to functional testing of web applications.

What the heck does [...] mean in your documenation?

Postby qamaster » Tue Sep 01, 2009 4:31 pm

Often I see the notation in your documenation [...]. What the
heck does that mean?
qamaster
 
Posts: 1
Joined: Tue Sep 01, 2009 4:27 pm

Re: What the heck does [...] mean in your documenation?

Postby eValid » Wed Sep 02, 2009 5:15 am

qamaster wrote:Often I see the notation in your documenation [...]. What the
heck does that mean?


Our apologies on this one -- we should have made it clearer.

The "[...]" notation means that you can have what's inside the brackets as an option.

For example, you can [not] answer the question directly if you want to be clever. And this sentence reads correctly either way: " ... can answer the question" or " ... can not answer the question". Does that answer the question?

The idea is to cut down on words and keep the context clear.

The eValid Team
eValid
 
Posts: 2396
Joined: Tue Jan 01, 2008 12:48 pm
Location: USA


Return to Desktop and Mobile Device Functional Testing

Design Downloaded from free phpBB templates | free website templates | Free Web Buttons