testing - AutoIt best practices / coding style -

-


testing - AutoIt best practices / coding style -

i maintain autoit project used automated testing of swing app. tests have 70 files. it's pretty hard maintain code without next "best practices" i'm trying create much functions possible (because of duplicate code) , constants (frequent changes) bud doesn't seem enough.

i have types of functions:

some general functions (insert text logging, select or read combobox.. ) some screen specific functions (fill 1 form.. ) some data/logic function - testing of app logic , info processing test case functions - combines previous 3 implement test scenario

autoit not have classes => no inheritance => oop principles hard aplicate ( :d clearly)

does have experince larger applications written in autoit? sentiment is, autoit scripts < 500 lines , wasn't selection big project.

it's shame, autoit doesn't have useful ide.

autoit developers want create sure functions written in autoit part of core library (in short: udfs) subject code style. can find standard here: http://www.autoitscript.com/autoit3/udfs/udf_standards.htm many programmers in community write autoit code in standard.

on subject of ide. scite time-tested code editor, ide performs adequate. there 2 other ides developed , maintained community:

a graphical debugger (f10 step next functionality) http://www.autoitscript.com/forum/topic/21834-graphical-autoit-debugger/

isn autoit studio http://www.autoitscript.com/forum/topic/136766-isn-autoit-studio/

the lastly 1 new, looks extremely promising , may work improve project.

finally, have note of warning. "oop principles hard apply", oo programmer should have strong core thought of how write non-oo code before learned oop. oo languages imperative @ core, should first-class imperative coder already. autoit imperative well.

a useful ide not solve problems! create them slightly easier manage.

i don't know heard autoit performs scripts under 500 lines, every time #include 1 of default libraries adding ~10000 lines of code. if can write proper code, build own libraries without adding complexity rest of code.

testing coding-style autoit

Comments

Post a Comment

Popular posts from this blog

How do I check if an insert was successful with MySQLdb in Python? -

-
How do I check if an insert was successful with MySQLdb in Python? - i have code: cursor = conn.cursor() cursor.execute(("insert new_files (videos_id, filename, " "is_processing) values (%s,%s,1)"), (id, filename)) logging.warn("%d", cursor.rowcount) if (cursor.rowcount == 1): logging.info("inserted values %d, %s", id, filename) else: logging.warn("failed insert values %d, %s", id, filename) cursor.close() fun is, cursor.rowcount always one, though updated database create videos_id unique key. is, insert fails because in tests same videos_id going appear (and when check database, nil inserted). whatever reason, rowcount 1 - logging.warn have spits out rowcount of 1. so, question: can utilize rowcount work out if insert went fine? if so, (presumably) doing wrong? otherwise, how check if insert went fine? your code not commit after modifications (your modifications rolled back). should...
Read more

delphi - blogger via idHTTP : error 400 bad request -

-
delphi - blogger via idHTTP : error 400 bad request - i'm trying post blogger using idhttp component, however, i'm getting "http/1.0 400 bad request" error. procedure tform1.button1click(sender: tobject); var request,response,req : tstringlist; auth,blogid : string; begin blogid := '00000000000000000000000'; request := tstringlist.create; response := tstringlist.create; req := tstringlist.create; idhttp1.request.connection := 'keep-alive'; idhttp1.request.contenttype := 'application/x-www-form-urlencoded'; idssliohandlersocket1.ssloptions.method := sslvsslv23; request.clear(); request.values['accounttype'] := 'google'; request.values['email'] := 'xxx@gmail.com'; request.values['passwd'] := 'yyy'; request.values['service'] := 'blogger'; response.text :=idhttp1.post('https://www.google.com/accounts/clientlogin',request); auth := resp...
Read more

postgresql - ERROR: operator is not unique: unknown + unknown -

-
postgresql - ERROR: operator is not unique: unknown + unknown - i have postgis database , have compute new values rows in new column. these values should average of values of several columns. query: insert bdps (da_m) values (avg('da_1'+'da_2'+'da_3'+'da_4'+'da_5'+'da_6'+'da_7')); in query bdps database, da_m new column , da_1 da_7 existing columns have double precision type. da_m created using alter table bdps add together column da_m double precision; i next error: error: operator not unique: unknown + unknown line 2: values (avg('da_1'+'da_2'+'da_3'+'da_4'+'da_5'+'da_6'+'da_7... ^ hint: not take best candidate operator. might need add together explicit type casts. ********** error ********** error: operator not unique: unknown + unknown sql state: 42725 hint: not take best candidate operator. might need add togethe...
Read more