gui interfaces / tables / script / question

Question

0.00/5 (No votes)

See more:

hello

question. is there a 'term' that is used to describe when a script checks for
a newly added (user input) into an existing 'table' ?

XFER6

Posted 11-Nov-14 4:29am

XFER6

Add a Solution

Comments

Sergey Alexandrovich Kryukov 11-Nov-14 10:34am

Why would you need a term for that? If this is to find something on the Web, better tell us what you are looking for.
—SA

XFER6 11-Nov-14 14:57pm

SA Thanks for your reply. Polling just once in the entire script. There is a gui
interface to a specific unit [ that is part of a perminant testbed ] which tests new s/w platforms on weekly basis. Using iTest software for script creation.
-----
hypothetical scenario below [ table ]

alarm name month day year hour minutes a.m. p.m.
---------- ------- --- ---- ---- ------- ---- ----
1 November 1 2014 7 00 *
2 November 2 2014 7 00 *
FISHING November 1 2014 4 00 *
-------------------------------------------------------------------------------
script below: attempting to verify FISHING with script once it has been saved
and applied to the table.

Action Description

describe :<target>;
click :id=messageArea;
[+]describe ://TR[3]/TD[1];
[-] analyze
contains FISHING
[-] assert $value==1
[-] When true
DeclareExecutionIssue OK:{auto_message_true};
PassTestifNotAlreadyFailed
[-] When false
DeclareExecutionIssue ERROR:{auto_message_false};
FailTest

CLOSE
---------------------------------------------------------------------------------
2 errors produced
1.) DeclareExecutionIssue Error:Specified target "<target>" was not found on the
browser page.
2.) [-]describe //TR[3]/TD[1]
[-]analyze step:contains FISHING: assert value==1
[-]assert value 0; assertion False
action DeclareExecutionIssueError; Response does not
contain "FISHING"
[-]action FAIL TEST

Sergey Alexandrovich Kryukov 11-Nov-14 15:06pm

I don't understand what is that. Did you read my Solution 1?
—SA

XFER6 11-Nov-14 15:18pm

SA -
Yes. Thank you for all of the information as well as your time !

XFER6

Sergey Alexandrovich Kryukov 11-Nov-14 15:34pm

You are welcome. Does it provide you with the background you want? Will you accept it formally (green "Accept" button)?
In all cases, your follow-up questions will be welcome.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-11-11T04:38:00

Why would you need a term for that? If this is to find something on the Web, better tell us what you are looking for.

I never heard about such term, but this is a part of "pull technology", in contrast to "push technology".
That means that "pulling" is a bad thing, this is periodic polling because of the draconian limitation of the model of the network communication. The server side is not "pushing" newly added modification to the client. This is a loose-loose situation: if you poll more frequently, you waste resources and traffic for nothing, if you poll rarely, you loose events in between.

This is a problem with the client-server database technologies and the Web; and some work-around solutions exist ("server push"). Too bad, you did not provide any information on the technologies you are using. For further detail, please see my past answer:
Application 'dashboard' for website accounts[^].

—SA