parsing failures in taurus csv

324 views
Skip to first unread message

ragesh ns

unread,
Mar 21, 2016, 7:51:57 AM3/21/16
to codename-taurus

while executing below scripts

---
execution:
- concurrency: 15
  ramp-up: 3s
  scenario: Login
scenarios:
  Login:
    data-sources:
    - delimiter: ','
      path: Login.csv
      quoted: false
      recycle: true
    requests:
    - body:
        companyCode: ''
        loginName: ${username}
        password: '********'
      headers:
        Accept: text/html, application/xhtml+xml, */*
        Accept-Encoding: gzip, deflate
        Accept-Language: en-IN
        Content-Type: application/x-www-form-urlencoded
        Pragma: no-cache
        Referer: http://${serverip}:${port}/iLogisticsNeo/login.jsp
        User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like
          Gecko
      label: Login
      method: POST
      url: http://${serverip}:${port}/iLogisticsNeo/spring/login_check
    store-cache: false
    store-cookie: false
    use-dns-cache-mgr: false

error logged 

D:\Python27\Scripts>bzt NeoLogin.yml
16:33:59 INFO: Taurus CLI Tool v1.2.0
16:33:59 INFO: Starting with configs: ['NeoLogin.yml']
16:33:59 INFO: Configuring...
16:33:59 INFO: No personal config: C:\Users\A-4604\.bzt-rc
16:33:59 INFO: Artifacts dir: D:\Python27\Scripts\2016-03-21_16-33-59.988000
16:34:00 INFO: Preparing...
16:34:00 ERROR: ValueError: invalid literal for int() with base 10: '${port}'
16:34:01 WARNING: Please wait for graceful shutdown...
16:34:01 INFO: Post-processing...
16:34:01 INFO: Artifacts dir: D:\Python27\Scripts\2016-03-21_16-33-59.988000
16:34:01 WARNING: Done performing with code: 1


Login.csv as follows:-

serverip,port,username,password
192.168.3.108,9491,DIVZ000001,Qq123456@
192.168.3.108,9491,DIVZ000001,Qq123456@
192.168.3.108,9491,DIVZ000001,Qq123456@
192.168.3.108,9491,DIVZ000001,Qq123456@
192.168.3.108,9491,DIVZ000001,Qq123456@


csv_data_issue.png

ta...@blazemeter.com

unread,
Mar 21, 2016, 10:34:43 AM3/21/16
to codename-taurus
Hi. It's similar to a bug, i'll check it in the closest time.

ta...@blazemeter.com

unread,
Mar 22, 2016, 1:36:51 AM3/22/16
to codename-taurus
Yes, this is a bug caused by combination of variables and jmeter requests. We'll fix it in nearest release (in 1-2 weeks).
Reply all
Reply to author
Forward
0 new messages