engine in engine
andrzejek
Polska
To remove the complexity of engines and writing them it would be a good idea to use engine in engine.
The main engine could hold all the required data, and other engine can be used for the STEPS passing all the data & variables to it. It would also allow to use some of the engines as "plugins" (like in latest Zennoposter updates).
[REGISTER_STEP1]
do normal posting
[LOGIN_STEP1]
engine=login_engine.ini
[STEP1]
engine=submit_engine.ini
The main engine could hold all the required data, and other engine can be used for the STEPS passing all the data & variables to it. It would also allow to use some of the engines as "plugins" (like in latest Zennoposter updates).
[REGISTER_STEP1]
do normal posting
[LOGIN_STEP1]
engine=login_engine.ini
[STEP1]
engine=submit_engine.ini
Comments
1. Send data to custom API in a STEP (like; selected variables, html response, headers).
2. API then can process the data and send back some kind of "API call" (and data) that SER can understand and translate to its steps!
[something]
type=extract
input=http://myapi.localhost:9000/login=%login%&htmlcontent=%htmlcontent%
But how can i pass the HTML response? Shall it be extracted with:
[htmlcontent]
type=extract
front1=<html
back1=html>
Even if yes, that can cause issues due to bad formatting in the website or some article about <html> ?
What if we could pass the whole response in post_data?
[something]
type=extract
input=http://myapi.localhost:9000/
post data=%html_data%
Or maybe:
[something]
; we send the response and the data in json encoded post request?
type=external
target=http://myapi.localhost:9000/
Then maybe:
submit success=here data that is checked by SER but if its not found try "something"|%something%