super({...{readableObjectMode: true}, ...opts})
^^^
SyntaxError: Unexpected token ...
I have installed node-v10.15.1-linux-x64 and running
npm install -g artillery
but it fails :
npm ERR! request to https://registry.npmjs.org/artillery failed, reason: write EPROTO 140216831190848:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl
any idea ?
qs to set the query string that way: https://artillery.io/docs/http-reference/#query-strings
🔊 A short announcement Artillery friends 🔊
This channel is closing down in favor of a new community discussion board on Spectrum - https://spectrum.chat/artillery-io/general/welcome-to-the-new-artillery-io-community~7e3184eb-aa2b-4b51-bb52-c94d80758f11 Gitter has been useful but Spectrum has a number of advantages, threads & search being the two critical ones. See you all over at https://spectrum.chat/artillery-io 👋
@ghost~5cc08ba2d73408ce4fbe92be currently it's not possible https://spectrum.chat/artillery-io/general/is-it-possible-to-have-a-socketio-query-with-random-number-for-each-connect~d01e5441-2640-4527-943d-8c639a320c37
@hassy "It's not possible at the moment, we'll file it as a bug (query is only evaluated once)"
Hi @jwingo1015 have you seen this part ? https://artillery.io/docs/http-reference/#logging
and if i do, write the test scenario in .yml file, and it's work. https://artillery.io/docs/getting-started/#running-the-test
// login.test.yml
config:
processor: './processor.js'
...
scenarios:
- name: 'Login success'
flow:
- post:
url: '/login'
beforeRequest: setLoginQuery
afterResponse: logRes
// processor.js
module.exports = {
setLoginQuery (requestParams, context, ee, next) {
requestParams.json = {
username: 'admin',
password: 'secret'
}
return next()
},
logRes (requestParams, response, context, ee, next) {
// I use this only for debugging
console.log(`response body : ${JSON.stringify(response.body)}`)
return next()
}
}capture to capturing an array ?
I don't think it supports it for now.
And I don't know your reason for having to only use capture :-/
capturewritten in the documentation The capture element must always have an as attribute which names the value for use in subsequent requests
which value will also be stored in the variables (as a string)
and the same thing when we useInline variables https://artillery.io/docs/script-reference/#inline-variables
orfunction-steps-in-a-flowhttps://artillery.io/docs/http-reference/#function-steps-in-a-flow
For alternative, we can handle it using "hooks", if you've read this section, https://artillery.io/docs/http-reference/#advanced-writing-custom-logic-in-javascript
explanation about processor, like the example I gave above.
nah not really, I don't think that's good, even though it's not an error, but it will break our expect.
You must store the id in config.variabel, not from the function process.
https://artillery.io/docs/script-reference/#inline-variables
and there are case examples that are a little close
https://artillery.io/docs/http-reference/#looping-through-an-array
but this value is set static.
if I were, it would be like this
// product.test.yml
scenarios:
- name: 'Fetch product store'
flow:
- log: "Get list store"
- get:
url: '/ecommerce/stores/'
afterResponse: extractStoreData
- loop:
- log: "Get product list of storeIds: {{ $loopElement }}"
- get:
url: '/ecommerce/stores/{{ $loopElement }}/products'
afterResponse: extractProductData
- loop:
- log: "Get detail product of storeId: {{ storeId }} with productId: {{ $loopElement }}"
- get:
url: '/ecommerce/stores/{{ storeId }}/products/{{ $loopElement }}'
over: productIds
over: storeIds
// processor.js
module.exports = {
extractStoreData (requestParams, response, context, ee, next) {
if (response.statusCode === 200) {
const res = JSON.parse(res.body) // if body contain as string we should parse to json object
const ids = []
// assume we only take 3 store data only
for (let i = 0; i < 3; i++) {
const store = res[i];
ids.push(store.id)
}
// now we stored in the variables (as an array of string id)
ctx.vars['storeIds'] = ids
}
return next()
},
extractProductData (requestParams, response, context, ee, next) {
if (response.statusCode === 200) {
...
// now we stored in the variables (as an array of string id)
ctx.vars['productIds'] = ids
ctx.vars['storeId'] = ctx.vars['$loopElement']
}
return next()
}
}Thats all variables we can handle on context context.vars['variable-name'].
I think you only need to create data object in an array with length from number of loops. Then you call the data object from processor base on index of loop,
you can catch it with
ctx.vars['$loopElement'].
@jwingo1015 yes you can.
And following from the example case you gave above:
// product.test.yml
scenarios:
- name: 'trying to create multiple products for one store'
flow:
- loop:
- post:
url: "/ecommerce/stores/{{ store_id }}/products"
headers:
authorization: "apikey {{ api_key }}"
beforeRequest: "setPostQuery"
expect:
- statusCode: 200
count: 100
// processor.js
const data = require('./data.json') // your sample data object in an array
module.exports = {
setPostQuery (req, ctx, ee, next) {
// ctx.vars['$loopCount'] is 1 - 100
// so, i recommend to using `$loopElement` to get index of count. ( 0 - 99)
// because array index starting from 0 in javascript
req.json = data[ctx.vars['$loopElement']]
return next()
}
}don't forget to read this: https://artillery.io/docs/http-reference/#looping-through-a-number-of-requests
