-
Notifications
You must be signed in to change notification settings - Fork 24
Description
乙醇老师,您好!
lazyman自动生成的用例目前运行的话,会全部失败。
mantis的用例是因为它的demo网站已经关闭,目前打不开了;
而百度+谷歌的用例也报错,应该是他们UI做了改变,找不到对应的元素。
我这边还有个问题,运行完用例后,./app/reports下并没有生成报告,似乎是一个Formatter组件被gem官方停用了。
请问您最近有打算升级lazyman的gem包吗?
谢谢!(我的邮件地址:[email protected])
以下是报错信息:
Microsoft Windows [版本 6.1.7601]
版权所有 (c) 2009 Microsoft Corporation。保留所有权利。
C:\Users\Administrator>cd e:\lazyman_project\mantis
C:\Users\Administrator>E:
e:\lazyman_project\mantis>lazyman go
run rspec from "."
Run options: include {:baidu=>true, :google=>true, :mantis=>true}
FFFFF
Failures:
- Baidu example show you how to use lazyman should search baidu using key wor
d
Failure/Error: result_page.first_result.should eq 'watir-webdriver_????????
?'
Watir::Exception::UnknownObjectException:
unable to locate element, using {:index=>0, :tag_name=>"h3"}(eval):1:in `process_watir_call'
./app/cases/baidu_and_google/baidu_example_spec.rb:15:in`block (2 levels
) in <top (required)>'
- Baidu example show you how to use lazyman should have correct search result
Failure/Error: result_page.first_result.should eq 'watir-webdriver_????????
?'
Watir::Exception::UnknownObjectException:
unable to locate element, using {:index=>0, :tag_name=>"h3"}
# (eval):1:in process_watir_call' # ./app/cases/baidu_and_google/baidu_example_spec.rb:21:inblock (2 levels
) in <top (required)>'
- Google example show you how to use lazyman should have correct search resul
t
Failure/Error: result_page = google_page.search_for @Keyword
Selenium::WebDriver::Error::InvalidElementStateError:
invalid element state: Element is not currently interactable and may not
be manipulated
(Session info: chrome=38.0.2125.122)
(Driver info: chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_6 -
(eval):1:in `process_watir_call'
./app/pages/google/google_page.rb:9:in`search_for'
./app/cases/baidu_and_google/google_example_spec.rb:12:in `block (2 level
s) in <top (required)>'
-
report issue login login should login
Failure/Error: my_view_page = login_page.login user, password
Watir::Exception::UnknownObjectException:
unable to locate element, using {:name=>"username", :tag_name=>"input or
textarea", :type=>"(any text type)"}
Shared Example Group: "login" called from ./app/cases/mantis/report_issue_s
pec.rb:7(eval):1:in `process_watir_call'
./app/pages/mantis/login_page.rb:10:in`login'
./app/cases/shared/login.rb:8:in `block (2 levels) in <top (required)>'
-
report issue report issue should create report
Failure/Error: report_issue_page.create_issue category, summary, desc do |p
age|
Watir::Exception::UnknownObjectException:
unable to locate element, using {:name=>"category_id", :tag_name=>"select
"}(eval):1:in `process_watir_call'
./app/pages/mantis/report_issue_page.rb:17:in`create_issue'
./app/cases/mantis/report_issue_spec.rb:18:in `block (3 levels) in <top (
required)>'
Deprecation Warnings:
The Lazyman::LazymanFormatter formatter uses the deprecated formatter interface
not supported directly by RSpec 3. To continue to use this formatter you must
install the rspec-legacy_formatters gem, which provides support for legacy for
matters or upgrade the formatter to a compatible version. Formatter added at: D
:/Ruby193/lib/ruby/gems/1.9.1/gems/rspec-core-3.1.7/exe/rspec:4:in `<top (requir
ed)>'
RSpec::Core::Configuration#treat_symbols_as_metadata_keys_with_true_values= is d
eprecated, it is now set to true as default and setting it to false has no effec
t.
If you need more of the backtrace for any of these deprecations to
identify where to make the necessary changes, you can configure
config.raise_errors_for_deprecations!, and it will turn the
deprecation warnings into errors, giving you the full backtrace.
2 deprecation warnings total
Finished in 34.06 seconds (files took 0.66804 seconds to load)
5 examples, 5 failures
Failed examples:
rspec ./app/cases/baidu_and_google/baidu_example_spec.rb:10 # Baidu example show
you how to use lazyman should search baidu using key word
rspec ./app/cases/baidu_and_google/baidu_example_spec.rb:18 # Baidu example show
you how to use lazyman should have correct search result
rspec ./app/cases/baidu_and_google/google_example_spec.rb:10 # Google example sh
ow you how to use lazyman should have correct search result
rspec ./app/cases/shared/login.rb:2 # report issue login login should login
rspec ./app/cases/mantis/report_issue_spec.rb:12 # report issue report issue sho
uld create report
e:\lazyman_project\mantis>