Chrome extension to generate code for automated feature tests.
- or -
Post a project like this$$
- Posted:
- Proposals: 1
- Remote
- #2262562
- Expired
Description
Experience Level: Intermediate
I would like to create a new Chrome Extension similar to https://github.com/polarblau/capycorder (available on the Chrome web store at https://chrome.google.com/webstore/detail/capycorder/niijdolnjmjdjakbanogihdlhcbhfkho .)
That project is unmaintained and has a number of outstanding issues, but I also understand how it works under the hood and I think it's easier to just make a fresh start.
— User visits a website.
— User "starts" recording by clicking the extension icon in the toolbar.
— Extension starts keeping track of any clicks, form changes, etc. that the user is performing on the page and across many different pages.
— The goal here is that it will later write these actions out as capybara feature test syntax, which looks like this:
```
visit '/sessions/new'
within("#session") do
fill_in 'Email', with: 'user@example.com'
fill_in 'Password', with: 'password'
end
click_button 'Sign in'
```
— At any point in this process, a user can also select text on the site and maybe select an option from the extension (maybe by clicking the icon again for a dropdown) to add an assertion to the outputted test code that ensures that the select text is present in a specific selector context, for example:
```
within('.alert') do
assert page.has_content?("some error message.")
end
```
— Whatever the ".alert" selector is, we need to ensure that it's unique on the page before we use it.
— When the user is done recording, they can click the icon again (maybe for a dropdown menu) and copy the test code to their clipboard.
What do you think? When we're done on this project, we actually want to release this project as open source and we could continue to pay you to maintain and develop it.
Best,
Andrew
That project is unmaintained and has a number of outstanding issues, but I also understand how it works under the hood and I think it's easier to just make a fresh start.
— User visits a website.
— User "starts" recording by clicking the extension icon in the toolbar.
— Extension starts keeping track of any clicks, form changes, etc. that the user is performing on the page and across many different pages.
— The goal here is that it will later write these actions out as capybara feature test syntax, which looks like this:
```
visit '/sessions/new'
within("#session") do
fill_in 'Email', with: 'user@example.com'
fill_in 'Password', with: 'password'
end
click_button 'Sign in'
```
— At any point in this process, a user can also select text on the site and maybe select an option from the extension (maybe by clicking the icon again for a dropdown) to add an assertion to the outputted test code that ensures that the select text is present in a specific selector context, for example:
```
within('.alert') do
assert page.has_content?("some error message.")
end
```
— Whatever the ".alert" selector is, we need to ensure that it's unique on the page before we use it.
— When the user is done recording, they can click the icon again (maybe for a dropdown menu) and copy the test code to their clipboard.
What do you think? When we're done on this project, we actually want to release this project as open source and we could continue to pay you to maintain and develop it.
Best,
Andrew
Andrew C.
100% (1)Projects Completed
3
Freelancers worked with
3
Projects awarded
0%
Last project
26 Jul 2021
United States
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies