14b7c10567
Capybara's native#send_key function is slow when it is passed a string longer than just a few characters. This often results in timeout issues and Capybara (falsely) reporting feature as failing. To fix this, we use the faster function #fill_in. This does not trigger JavaScript events on the input, so we manually trigger them after fill_in by just sending a single key. This can be any key but since we do not want to modify the text in the input, non-text keys should be used. For a list of non-text keys, see http://www.rubydoc.info/github/jnicklas/capybara/Capybara%2FNode%2FElement%3Asend_keys There is an alternative to the above: 1) Use #fill_in to enter all text except for the last character: fill_in ..., with: "#{status_message_text} #{txt[0..-2]}" 2) And then use #send_key to send that last character: find("#status_message_text").native.send_key(txt.last) At the moment, both approaches work equally well but the second approach is documented here just in case it becomes relevant in the future. |
||
|---|---|---|
| app | ||
| bin | ||
| config | ||
| db | ||
| features | ||
| graphics | ||
| lib | ||
| public | ||
| script | ||
| spec | ||
| tmp/pids | ||
| vendor | ||
| .codeclimate.yml | ||
| .editorconfig | ||
| .eslintrc | ||
| .foreman | ||
| .gitignore | ||
| .haml-lint.yml | ||
| .pronto.yml | ||
| .rspec | ||
| .rubocop.yml | ||
| .ruby-gemset | ||
| .ruby-version | ||
| .scss-lint.yml | ||
| .slugignore | ||
| .travis.yml | ||
| AUTHORS | ||
| browserlist | ||
| Changelog.md | ||
| CODE_OF_CONDUCT.md | ||
| config.ru | ||
| COPYRIGHT | ||
| FederationProcfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| LICENSE | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| redis-integration1.conf | ||
| redis-integration2.conf | ||
diaspora*
A privacy-aware, distributed, open source social network
master: 
next-minor: 
|
develop: 
|
Project site | Wiki | Bugtracker | Discussions and Support | License | Authors
Installation
You don't have to install diaspora* to use the network. There are many servers connected to diaspora*s network which are open to anyone, and you can create an account on one of these servers. Have a look at our tips for finding a home, or you can just go straight to the list of open servers to sign up.
Want to own your data and install diaspora*? Whether you just want to try it out, want to install it on your server or want to contribute and need a development setup, our installation guides will get you started!
Questions?
Have a look at our FAQs for users, for pod administrators or for developers.
Still haven't found an answer? Talk to us! Read how we communicate. We're here to answer all your questions.
Contribute
To keep diaspora* growing and improving we need all help we can get. Whether you can contribute code, ideas, translations, bug reports or simply extend the community as a helpful user or pod administrator, your help is welcome!
Everyone interacting in diaspora’s codebases, issue trackers, chat rooms, the wiki, and the Discourse is expected to follow the diaspora* code of conduct.
Security
Found a security issue? Please disclose it responsibly. We have a team of developers listening to security@diasporafoundation.org. The PGP fingerprint is AB0D AB02 0FC5 D398 03AB 3CE1 6F70 243F 27AD 886A.