Acceptance Testing Rails using a "Testing API" for client side state control -


i evaluating how test rather big , complex web application, based on rails 4 on server side , emberjs on client side. in our app, client exclusively communicates through restful json api server.

we did lot of unit testing based on konacha far , willing setup integration/acceptance tests too. not sure whether should start writing end-to-end tests, tests including running instance of our server, or whether should go integration testing api , client side separately.

our preferred choice @ moment end-to-end testing, because fear in case of integration testing api , client separately have twice effort of creating , maintaining tests , there might tiny, little specialities of comunication between api , client not catch.

well, modern & fast testing frameworks konacha, don't want use selenium. not because feels little bit old, because performance quite poor. still need control instantiation of mock data on server , reset of server, why came following approach:

we implemented testing api conceptually used control state of server, e.g. has following methods:

get /api/test/setup  # simple bootstrapping of database, e.g. populate table iso language codes etc... /api/test/reset  # reset database, using `database_cleaner` gem

a konacha test case call setup , reset, before , after each test case respectively.

what think approach?

not sure call test of api , client separately, if think running kind of test, still should got end-to-end test.

so yes, think idea of going end-to-end testing good.

your idea of setting simple commands allow test automation system (the setup , reset commands) well. prepared add more during automation - while end-to-end-test conceptually black-box test, in reality it's grey-box test, i.e. need access internal state of system. call "operation , maintenance interface" of system under test.


Comments

Post a Comment

Popular posts from this blog

Android layout hidden on keyboard show -

i have strange problem layout. when tap on edittext , keyboard shown edittext stay on bottom , when tap on to hide keyboard , keyboard hides , edittext go should when want input text. when tap again, keyboard shown , edittext goes down behind keyboard... <relativelayout android:layout_width="match_parent" android:layout_height="match_parent" > <scrollview android:layout_width="match_parent" android:layout_height="fill_parent" android:above="@+id/rl_commands"> <textview android:layout_width="match_parent" android:layout_height="wrap_content"/> </scrollview> <relativelayout android:layout_width="match_parent android:layout_height="24dp" android:id="@+id/rl_commands" android:alignparentbottom="true">
Read more

google app engine - 403 Forbidden POST - Flask WTForms -

i have flask application running on google app engine. trying submit form built using wtform , keep getting following error. 403 forbidden: don't have permission access requested resource. either read-protected or not readable server. location.html (part of code) <form method=post action="/home/location"> .... <button type="submit" class="btn btn-primary" value="submit"> directions </button> </form> main.py @app.route('/home/location', methods=['post', 'get']) def location(): form = cfcdirections.direction(request.form) print(request.method) if request.method == 'post' , form.validate(): print("after if") directions = cfcdirections() street_no = directions.no street = directions.street suburb = directions.suburb postcode = directions.postcode
Read more

c - Why would PK11_GenerateRandom() return an error -8023? -

i looking through internet trying find source of pk11_generaterandom() function see why function fail. have program uses function when moved new flavor of linux, fails after forking ( fork() ) since not believe there problem nss, suspect doing incorrectly disregarded in older versions of linux new 1 there issue. the openssl package same on 'good' , 'bad' server: openssl 0.9.8e-fips-rhel5 01 jul nss rpm differs though. 'good' has nss-3.12.2.0-2.el5 and bas has version nss-3.15.3-4.el5_10 the 'good' server uses quite obsolete linux: linux 2.6.18-128.el5 #1 smp wed jan 21 08:45:05 est 2009 x86_64 x86_64 x86_64 gnu/linux enterprise linux enterprise linux server release 5.3 (carthage) red hat enterprise linux server release 5.3 (tikanga) the 'bad' server newer: linux bad 2.6.18-371.4.1.el5 #1 smp wed jan 29 11:05:49 pst 2014 x86_64 x86_64 x86_64 gnu/linux oracle linux server release 5.10 red hat enterprise linux server release
Read more