...inserito direttamente nelle proprie pagine web (o negli appositi file js)?
In genere si tratta di simulare click del mouse che richiamano ad esempio determinate funzioni, e quindi verificarne il corretto funzionameto, ecc.
Quali strumenti dovrei usare?
Non capisco la domanda... ma la pagina chi la usera'? se e' destinata agli esseri umani trova un umano che faccia click col mouse dove serve
Il guaio per i poveri computers e' che sono gli uomini a comandarli.
Attenzione ai titoli delle discussioni: (ri)leggete il regolamento
Consultate la discussione in rilievo: script / discussioni utili
Usate la funzione di Ricerca del Forum
Lo strumento pi comunemente usato la console javascript del browser, cui si accede con la combinazione CTRL+SHIFT+J
La console ti segnaler gli errori eventualmente riscontrati. Per fare debug puoi scrivere nei log della console tramite il metodo log() dell'oggetto console:
codice:console.log(variabile_da_verificare);
Oppure usare gli alert:
codice:alert(variabile_da_verificare);
quindi, dopo aver introdotto un aggiornamento, se in 50 pagine devo controllare ad es. la corretta apertura di un popup, devo andarmele a testare una per una?Originariamente inviata da lucavizzi
Direi che controllato un popup, controllati tutti...
E se per aprire quel popup (o fare qualche altra cosa) servono anche nuovi script aggiuntivi, come faccio ad assicurarmi di aver inserito il nuovo riferimento in tutte le pagine interessate?
Inoltre voglio anche testare l'integrit generale di un sito: verificare il funzionameto dei link ed interazioni varie.
Finora ho usato Selenium (anche se non mi mai piaciuto pi di tanto) ma con le nuove release di firefox non funziona
astros il tuo non mi sembra un reale problema js.
ad ogni modo come sistemi di test ci sono
http://angular.github.io/protractor/#/
http://karma-runner.github.io/
http://busterjs.org/
Ciro Marotta - Programmatore JAVA - PHP
Preferisco un fallimento alle mie condizioni che un successo alle condizioni altrui.
Cioe' ?
+ sudo npm install -g protractor
–€ •–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘•Ÿ
WARN engine protractor@5.1.2: wanted: {"node":">=6.9.x"} (current: {"node":"4.2.6","npm":"3.5.2"})
WARN engine protractor@5.1.2: wanted: {"node":">=6.9.x"} (current: {"node":"4.2.loadDep:webdriver-manager – •–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–‘–‘–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ •Ÿ
WARN engine blocking-proxy@0.0.5: wanted: {"node":">=6.9.x"} (current: {"node":"loadDep:webdriver-manager –Œ •–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–‘–‘–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ •Ÿ
WARN engine jasminewd2@2.1.0: wanted: {"node":">= 6.9.x"} (current: {"node":"4.2loadDep:webdriver-manager –Œ •–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–‘–‘–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ •Ÿ
WARN engine selenium-webdriver@3.0.1: wanted: {"node":">= 6.9.0"} (current: {"noloadDep:webdriver-manager –„ •–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–‘–‘–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ •Ÿ
WARN engine webdriver-manager@12.0.6: wanted: {"node":">=6.9.x"} (current: {"nodloadDep:uuid †’ get –Œ •–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ– ˆ–ˆ–ˆ–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ •Ÿ
WARN engine hawk@6.0.2: wanted: {"node":">=4.5.0"} (current: {"node":"4.2.6","np/usr/local/bin/protractor -> /usr/local/lib/node_modules/protractor/bin/protractor
/usr/local/bin/webdriver-manager -> /usr/local/lib/node_modules/protractor/bin/webdriver-manager
/usr/local/lib
”””€”€ protractor@5.1.2
+ webdriver-manager update
/usr/bin/env: "node": File o directory non esistente
+ webdriver-manager start
/usr/bin/env: "node": File o directory non esistente
+ proactor conf.js
./test.sh: riga 8: proactor: comando non trovato
+ sudo npm install karma
/mnt/common2/pending/karma
”””€”€ karma@1.7.1
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.2
npm WARN enoent ENOENT: no such file or directory, open '/mnt/common2/pending/karma/package.json'
npm WARN karma No description
npm WARN karma No repository field.
npm WARN karma No README data
npm WARN karma No license field.
+ ./node_modules/karma/bin/karma start
/usr/bin/env: "node": File o directory non esistente
+ sudo npm install -g buster
npm WARN deprecated graceful-fs@2.0.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated minimatch@0.1.5: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated connect@2.7.2: connect 2.x series is deprecated
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
loadDep:uuid †’ resolveWit –„ •–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–ˆ–‘–‘–‘– ‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ –‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘–‘ •Ÿ
WARN engine hawk@6.0.2: wanted: {"node":">=4.5.0"} (current: {"node":"4.2.6","np/usr/local/bin/buster -> /usr/local/lib/node_modules/buster/bin/buster
/usr/local/bin/buster-server -> /usr/local/lib/node_modules/buster/bin/buster-server
/usr/local/bin/buster-autotest -> /usr/local/lib/node_modules/buster/bin/buster-autotest
/usr/local/bin/buster-test -> /usr/local/lib/node_modules/buster/bin/buster-test
/usr/local/bin/buster-static -> /usr/local/lib/node_modules/buster/bin/buster-static
/usr/local/bin/buster-ci -> /usr/local/lib/node_modules/buster/bin/buster-ci
> contextify@0.1.15 install /usr/local/lib/node_modules/buster/node_modules/contextify
> node-gyp rebuild
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:354:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-96-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/buster/node_modules/contextify
gyp ERR! node -v v4.2.6
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN install:contextify@0.1.15 contextify@0.1.15 install: `node-gyp rebuild`
npm WARN install:contextify@0.1.15 Exit status 1
> ref@1.0.2 install /usr/local/lib/node_modules/buster/node_modules/ref
> node-gyp rebuild
/bin/sh: 1: node: not found
gyp: Call to 'node -e "require('nan')"' returned exit status 127 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:354:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 4.4.0-96-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /usr/local/lib/node_modules/buster/node_modules/ref
gyp ERR! node -v v4.2.6
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
npm WARN install:ref@1.0.2 ref@1.0.2 install: `node-gyp rebuild`
npm WARN install:ref@1.0.2 Exit status 1
/usr/local/lib
”””€”€ buster@0.7.18
npm WARN optional Skipping failed optional dependency /buster/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@0.3.8
+ buster-test
/usr/bin/env: "node": File o directory non esistente
Ultima modifica di astros3; 25-09-2017 a 09:40
niente?
Permessi di invio
Rispondi quotando