mpociot / laravel-testtools

Chrome extension to generate Laravel integration tests while using your app.

Working on What The Diff - Your AI-powered code review tool

laravel-testtools's Issues

Image upload support

Did the extension support uploading images though the test scenario?

Use Webpack / vue-loader / ES2015/ npm build scripts

Right now the JS code of the extension isn't very well structured.

Maybe we could introduce webpack in combination with vue-loader to this extension.
This would also allow us to make use of babel.js to write some nicer looking ES2015 code.

Any help on this topic is greatly appreciated.

Textareas are ignored

Apply the jQuery event listener to textareas too.

Add LICENSE file

There should probably be a LICENSE file that contains a copyright (that has to be kept if people modify the extension according to MIT's terms). Currently there's no copyright statement, so nothing to keep except for the notice in the README?

Getting TypeError: Failed to fetch

When I installed the extension I'm getting a error in the console.

Uncaught (in promise) TypeError: Failed to fetch
    at TypeError (native)

Chrome Version 49.0.2623.112 m
Extension Version: 0.2.0

The Version before 0.2.0 which was 0.1.2 works.

I also tested this extension on a brand new install of vivaldi 1.0 & same problem.

firefox support?

is there going to compatible Firefox WebExtension?

Thanks

require is not defined

Hey, I'm using the extension on chrome (v58.0.3029.81, OS: win7) and I got this error:
Uncaught ReferenceError: require is not defined at content.js:1.
ideas? thx.

Generating empty string when button is pressed

I clicked on a button which has Arabic language text:

<input type="submit" value="سجل">

The recorder did capture it as empty string:

$this->press('');

Add Tests

We should write tests for the extension.

Chrome App Unresponsive

Sorry if this isn't the right place for this ...

Since the last update, I've noticed that when I tried to use the Laravel TestTools, the screen I get looks like the attached. Clicking on the buttons doesn't seem to do anything.

Disable vue.js message

Hey, the plugin always shows the very annoying vue message in the console.

Download the Vue Devtools for a better development experience: https://github.com/vuejs/vue-devtools

Please disable it. The internet says it can be done like this:

var Vue = require('vue');
Vue.config.devtools = false;

Is this being actively worked on?

Love the extension has made writing tests so much easier, was wondering if there is any active work going on with it? I can see some easy simple features to add to this to make it even better!

Thank you.

Use CircleCI to automatically build the extension

In order to release updates faster we should integrate CircleCI and use the Chrome Web Store API to upload new extension releases.

This way commits to the master branch could automatically result in an extension update.

Feature Request: Support Laravel Dusk

Hey, great plugin!

Any plans to support laravel dusk code generation instead ? Thanks

Add "Type" to menu

It would be nice if we could add a "Type" option so we could put in our own custom text.

Factory not working - nothing happens

Import of Laravel's 5.6 default UserFactory.php from database/factories folder worked successfully.

But when I click on the new menu entry "Factories --> App\User::Class --> Create Model:App\User::class" nothing happens except the test's function body is cleared.

What should happen? And why it does not?

<?php
// UserFactory.php
use Faker\Generator as Faker;

$factory->define(App\User::class, function (Faker $faker) {
    return [
        'name' => $faker->name,
        'email' => $faker->unique()->safeEmail,
        'password' => '$2y$10$TKh8H1.PfQx37YgCzwiKb.KjNyWgaHb9cbcoQgdIVFlYg7B77UdFm', // secret
        'remember_token' => str_random(10),
    ];
});

Wrong faker code generation while in dusk mode

While dusk is enabled, it generates wrong code when a faker option is selected:

use Tests\DuskTestCase;
use Laravel\Dusk\Browser;

class LoginTest extends DuskTestCase
{
    /**
     * @var FakerGenerator
     */
    protected $faker;
    
    /**
     * Setup faker
     */
    public function setUp()
    {
        parent::setUp();
        $this->faker = \Faker\Factory::create();
    }
    /**
     * My test implementation
     */
    public function testHierarchyIsFantastic()
    {

        $this->browse(function (Browser $browser) {
            $browser->visit('/login');
            $this->type(email, '$this->faker->email'); // <--bad generated code:
            // $this instead of $browser and apostrophes on wrong argument
        });

    }
}

Expected:

$browser->type('email', $this->faker->email);

Issue in renaming tests

• Press Rename Test button
• Press Cancel button in Rename Test popup

Expected result: Nothing should be changed in test code
Actual result: Test name is changed to "testnull"

Name the test class

Ability to add class name so when a user copies to the clipboard it is a seemless paste vs pasting and removing ExampleTest

Some suggestions for possible Selenium server support

This is a great package! I think it is going to be a huge timesaver.

I have no experience with Chrome extension development but I had a bit of a dig around and kind of understand how this extension works.

There are a couple of things that I don't immediately understand:

1. Press events can be added by clicking a submit button or through the right click menu; why aren't all press events added? I think all press() events should be added, and if the location changes also add seePageIs()? This would go a long way to supporting JavaScript interactions (with Selenium).
2. I'm wanting to do selenium testing, and besides point 1 above, the only other drawback is that the default template from Jeffrey Way's package is a little different to https://github.com/laracasts/Integrated/wiki/Examples. Perhaps allowing CRUD of templates and setting of a default would be the best all round solution, as well as toggling camel case / underscores? Or maybe just supporting a couple of common options out of the box.

I'm going to take the opportunity to dive into extensions and see if I can figure out how to scratch my own itch, will send PRs if I develop anything useful!

Multiple Tests Per Class

"Add Test" so that one can make multiple tests per "session" without copy and pasting each function

Test Setup wrong call to generate faker

I was having a few issues with the generated test code and noticed changing the following fixed it:

public function setUp() { parent::setUp(); $this->faker = new Faker\Generator(); }

to

public function setUp() { parent::setUp(); $this->faker = \Faker\Factory::create(); }

Images on the introduction post are broken

Link: http://marcelpociot.de/blog/2016-03-21-laravel-testtools

Record button disappeared in latest release?

I opened up the test tools today, and saw the addition of ability to select the 3 standard options for middleware / database handling (cool!), but my record button seems to be missing.

Screen shot attached (hopefully!)

Chrome version Version 49.0.2623.112 (64-bit)
Extension version 0.2.0