Перейти к содержимому

ivk

Регистрация: 15 ноя 2008
Offline Активность: 05 янв 2012 09:01
-----

Мои сообщения

В теме: Автоматический отлов ошибок JavaScript

19 ноября 2008 - 12:00

Посмотрел, возможности достаточно интересные, но сразу смутило то, что работает только под Windows и Mac... Спасибо, посмотрю поподробнее что там внутри.


1. JS include files can be checked by JSLint and PHP by Code_Sniffer before Selenium to make sure syntax and coding standards are fine.

My link points to a way to check JS after is was build by PHP into HTML but before it was sent to browser. You are right you will not test it inside browser. This is to check JS which is embedded into PHP code - this can not be checked with step 1.

Can you post page sample with what you want to catch? Something which is fine in one browser but brakes another one when loaded into it?
I will check it with Lint before sending to browser and think on how to catch it in browser if JSlint will not.

В теме: Автоматический отлов ошибок JavaScript

18 ноября 2008 - 13:04

Did not you think of using JSLint on server like described here.
You can output JSLint output instead of page, screenshot it and record it in log.

I wouldn't do it on live systems but you can control it (enable while under test and disable on live systems) by just commenting it out in a common include file. Right?

Igor Kryltsov