Code Monkey home page Code Monkey logo

lebowski's People

Contributors

dessy avatar jasonpgignac avatar mlcohen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

lebowski's Issues

Error accessing SproutCore object after reloading window

calling window.location.reload() blows away all the objects currently in the JavaScript engine's heap. When the page is reloaded a new SproutCore object and application objects are created. The Lebowski framework in the mean time is still referencing the old SproutCore object and root application object, so when making a request for some object and its property, the framework gets confused since it can no longer access those objects

IOS compatibility

Is lebowski compatible with IOS devices? Is it possible to test for the iphone & ipad? How?

Strange behavior when testing with IE 8

I just am getting the following false error with IE8:

Did not get expected type 'SC.ButtonView' for path 'authPage.authPane.signinView.actionButton'. Instead got object: SC.ButtonView

Actions drag_before and drag_after don't work

When trying to drag a list item view before or after another list item view within the same list using drag_before or drag_after, nothing happens.

Problem occurs in SproutCore 1-4-stable

exec_in_context loops should ensure the application context always switches back after the loop is finished.

If some Rspec fails (or anything else for that matter), exec_in_context doesn't reset the application context properly, and large numbers of tests afterwards start to fail.

Fix is basically to wrap the code in ensure blocks.

In Lebowski::Foundation::Support::ApplicationContextManager

  def exec_in_context(app, app_name=nil, &block)
    previous_app_context = @current_application_context.clone
    switch_application_context_to app, app_name
    yield app
  ensure
    switch_application_context_to previous_app_context[:app], previous_app_context[:app_name]
  end

  def exec_driver_in_context(app, &block)
    previous_app_context = nil
    if not has_current_application_context?(app)
      previous_app_context = @current_application_context.clone
      switch_application_context_to app
    end

    yield @driver

  ensure
    if not previous_app_context.nil?
      switch_application_context_to previous_app_context[:app], previous_app_context[:app_name]
  end

There are more elegant ways of doing it probably.

trace: true output is way too verbose

trace: true should be useful for Ki users. Right now, it's got a whole bunch of logging info that's only useful for people writing Ki itself. Please clean it up (perhaps add a second mode, traceAll: true that has the stuff that's there now).

What I want to know is: which event/actions were sent to the statechart, which states were given a chance to handle the event, which state did handle the event OR that the event was ignored, and finally which transition was specified (if any) along with the exit/enterState calls that are made. This allows me to fully trace user statechart code and see exactly what's happening.

Thanks!

Lebowski does not work with rspec 2.6.0

I am trying to use Lebowski in a project that requires rspec 2.6.0+. Bundler cannot install Lebowski in my project due to the requirement that Lebowski rspec (~> 2.5.0). I can hack my way around that, but I would love to use Lebowski's rspec integration.

Any plans to get this updated to work with rspec 2.6 any time soon?

--singleWindow issues with FF

I am experimenting different testing results when using --singleWindow in FF 3.6.20

Lebowski seems to fail to "click" a segment view when in singleWindow mode.

When running without the switch it all works fine.

Without having looked into this, I think there is a click positioning issue.

I also have the feeling that scrolling up/down has something to do. FF seems to scroll down when Lebowski updates controls otherwise not visible in the page.

has anybody also experienced this?

suggestion: add a Gemfile to standAlone example, +also include the sproutcore version.

~/RAILS/SPROUT/Lebowski/examples/hello_world/app$ sc-server
/home/dao01/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems.rb:267:in activate': can't activate rack (= 1.0.1) for [], already activated rack-1.2.2 for [] (Gem::LoadError) from /home/dao01/.rvm/rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:46:inblock in require'

Unable to access SC objects when switching between SproutCore applications

When there are two or more SC apps on the same domain, switching between them causes the framework to fail. This is due to the framework still retaining a reference to the SC objects in the first SC application that we started using the framework. Need to update the application context when switching between SC apps.

Trying to run scui samples with rspec 2

Greetings. I'm trying to run the SCUI samples. If I run the lebowski-spec command, I get a 'gem_original_require' error as it's looking for the lib/spec directory. If I change the first line in the respective spec files to point to lib/rspec instead, rougly half the samples pass for most of the sample apps. I tried switching to 1.9.2 from REE per the readme. I got 'TestApp.getPath("mainPage.mainPane") is undefined' with 1.9.2. Are these samples supposed to run with Rspec 2? What ruby version? In a related question, will the examples be updated to work with Sproutcore 1.5? Thanks -- Paul

Lebowski Framework unable to create specific proxies in IE 7 and IE 8

When running Lebowski with Internet Explorer versions 7 or 8, the framework is unable to detect the specific type of object being proxied. This is because in IE, the SproutCore framework can't detect what class an object comes from, so an "Anonymous" class name is applied instead. When Lebowski gets the "Anonymous" class name, it just defaults and returns a basic ProxyObject instance. Since this is a problem with SproutCore, not Lebowski, deeper investigation will have to be done in SC to resolve this problem.

segmentItem.selected? fail

This is true:

  @mainTabs.segmentedView.childViews[1].isSelected.should be_true

This is false:

  @mainTabs.segmentedView.buttons[1].selected?.should be_true

Am i using assertion wrong or there is some lebowski bug? :)

Lebowski fails using Ruby 1.9.2

When running Lebowski with Ruby v1.9.2 loading errors occur. The problem seems to stem from the selenium client. If you down grade to Ruby v1.9.1 you should be able to run the scripts without any problems. This issue is being looked into.

SC 1.6 support

Is there support for the latest SC 1.6 version?

We have migrated our service from 1.5, and are about to migrate the Lebowski tests.

Some controls seem to work, others seem to be broken.

Is SC 1.6 supported?

Lebowski fails using RSpec v2.*

Lebowski fails when the RSpec gem v2.* is installed. The following error appears:

lebowski-0.2.1/bin/lebowski-
spec:19:in `require': no such file to load -- spec (LoadError)

spec is the old RSpec library name for RSpec 1.. In RSpec 2. the library name is rspec

Multiple actions delivered to state

I am still investigating it, but my statechart seems to be receiving several callbacks for a sendAction call.

I am getting the callback function called 3/4 times (at the same state).

My startechart is using all possible features: concurrent states, history states, plug ins, hierarchies of states, etc. I also find useful sending actions from within states...

Maybe I am doing something wrong... may be there is am issue. Is there any case

Is there any known issue (or misuse) that would trigger this situation?

SproutCore 1.5 support?

I'll admit I haven't tried it, but the README indicated it was 1.4.x only. Any ETA or info on what needs to be done?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.