kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/development/testing_guide/frontend_testing.md

37 KiB
Raw Blame History

Frontend testing standards and style guidelines

There are two types of test suites you'll encounter while developing frontend code at GitLab. We use Karma and Jasmine for JavaScript unit and integration testing, and RSpec feature tests with Capybara for e2e (end-to-end) integration testing.

Unit and feature tests need to be written for all new features. Most of the time, you should use RSpec for your feature tests.

Regression tests should be written for bug fixes to prevent them from recurring in the future.

See the Testing Standards and Style Guidelines page for more information on general testing practices at GitLab.

Jest

We have started to migrate frontend tests to the Jest testing framework (see also the corresponding epic).

Jest tests can be found in /spec/frontend and /ee/spec/frontend in EE.

When should I use Jest over Karma?

If you need to update an existing Karma test file (found in spec/javascripts), you do not need to migrate the whole spec to Jest. Simply updating the Karma spec to test your change is fine. It is probably more appropriate to migrate to Jest in a separate merge request.

If you need to create a new test file, we strongly recommend creating one in Jest. This will help support our migration and we think you'll love using Jest.

As always, please use discretion. Jest solves a lot of issues we experienced in Karma and provides a better developer experience, however there are potentially unexpected issues which could arise (especially with testing against browser specific features).

Differences to Karma

  • Jest runs in a Node.js environment, not in a browser. Support for running Jest tests in a browser is planned.
  • Because Jest runs in a Node.js environment, it uses jsdom by default. See also its limitations below.
  • Jest does not have access to Webpack loaders or aliases. The aliases used by Jest are defined in its own config.
  • All calls to setTimeout and setInterval are mocked away. See also Jest Timer Mocks.
  • rewire is not required because Jest supports mocking modules. See also Manual Mocks.
  • No context object is passed to tests in Jest. This means sharing this.something between beforeEach() and it() for example does not work. Instead you should declare shared variables in the context that they are needed (via const / let).
  • The following will cause tests to fail in Jest:
    • Unmocked requests.
    • Unhandled Promise rejections.
    • Calls to console.warn, including warnings from libraries like Vue.

Limitations of jsdom

As mentioned above, Jest uses jsdom instead of a browser for running tests. This comes with a number of limitations, namely:

See also the issue for support running Jest tests in browsers.

Debugging Jest tests

Running yarn jest-debug will run Jest in debug mode, allowing you to debug/inspect as described in the Jest docs.

Timeout error

The default timeout for Jest is set in /spec/frontend/test_setup.js.

If your test exceeds that time, it will fail.

If you cannot improve the performance of the tests, you can increase the timeout for a specific test using setTestTimeout.

import { setTestTimeout } from 'helpers/timeout';

describe('Component', () => {
  it('does something amazing', () => {
    setTestTimeout(500);
    // ...
  });
});

Remember that the performance of each test depends on the environment.

Manual module mocks

Jest supports manual module mocks by placing a mock in a __mocks__/ directory next to the source module. Don't do this. We want to keep all of our test-related code in one place (the spec/ folder), and the logic that Jest uses to apply mocks from __mocks__/ is rather inconsistent.

Instead, our test runner detects manual mocks from spec/frontend/mocks/. Any mock placed here is automatically picked up and injected whenever you import its source module.

  • Files in spec/frontend/mocks/ce will mock the corresponding CE module from app/assets/javascripts, mirroring the source module's path.
    • Example: spec/frontend/mocks/ce/lib/utils/axios_utils will mock the module ~/lib/utils/axios_utils.
  • Files in spec/frontend/mocks/node will mock NPM packages of the same name or path.
  • We don't support mocking EE modules yet.

If a mock is found for which a source module doesn't exist, the test suite will fail. 'Virtual' mocks, or mocks that don't have a 1-to-1 association with a source module, are not supported yet.

Writing a mock

Create a JS module in the appropriate place in spec/frontend/mocks/. That's it. It will automatically mock its source package in all tests.

Make sure that your mock's export has the same format as the mocked module. So, if you're mocking a CommonJS module, you'll need to use module.exports instead of the ES6 export.

It might be useful for a mock to expose a property that indicates if the mock was loaded. This way, tests can assert the presence of a mock without calling any logic and causing side-effects. The ~/lib/utils/axios_utils module mock has such a property, isMock, that is true in the mock and undefined in the original class. Jest's mock functions also have a mock property that you can test.

Bypassing mocks

If you ever need to import the original module in your tests, use jest.requireActual() (or jest.requireActual().default for the default export). The jest.mock() and jest.unmock() won't have an effect on modules that have a manual mock, because mocks are imported and cached before any tests are run.

Keep mocks light

Global mocks introduce magic and can affect how modules are imported in your tests. Try to keep them as light as possible and dependency-free. A global mock should be useful for any unit test. For example, the axios_utils and jquery module mocks throw an error when an HTTP request is attempted, since this is useful behaviour in >99% of tests.

When in doubt, construct mocks in your test file using jest.mock(), jest.spyOn(), etc.

Karma test suite

GitLab uses the Karma test runner with Jasmine as its test framework for our JavaScript unit and integration tests.

JavaScript tests live in spec/javascripts/, matching the folder structure of app/assets/javascripts/: app/assets/javascripts/behaviors/autosize.js has a corresponding spec/javascripts/behaviors/autosize_spec.js file.

Keep in mind that in a CI environment, these tests are run in a headless browser and you will not have access to certain APIs, such as Notification, which will have to be stubbed.

Best practices

Naming unit tests

When writing describe test blocks to test specific functions/methods, please use the method name as the describe block name.

// Good
describe('methodName', () => {
  it('passes', () => {
    expect(true).toEqual(true);
  });
});

// Bad
describe('#methodName', () => {
  it('passes', () => {
    expect(true).toEqual(true);
  });
});

// Bad
describe('.methodName', () => {
  it('passes', () => {
    expect(true).toEqual(true);
  });
});

Testing promises

When testing Promises you should always make sure that the test is asynchronous and rejections are handled. Your Promise chain should therefore end with a call of the done callback and done.fail in case an error occurred.

// Good
it('tests a promise', done => {
  promise
    .then(data => {
      expect(data).toBe(asExpected);
    })
    .then(done)
    .catch(done.fail);
});

// Good
it('tests a promise rejection', done => {
  promise
    .then(done.fail)
    .catch(error => {
      expect(error).toBe(expectedError);
    })
    .then(done)
    .catch(done.fail);
});

// Bad (missing done callback)
it('tests a promise', () => {
  promise.then(data => {
    expect(data).toBe(asExpected);
  });
});

// Bad (missing catch)
it('tests a promise', done => {
  promise
    .then(data => {
      expect(data).toBe(asExpected);
    })
    .then(done);
});

// Bad (use done.fail in asynchronous tests)
it('tests a promise', done => {
  promise
    .then(data => {
      expect(data).toBe(asExpected);
    })
    .then(done)
    .catch(fail);
});

// Bad (missing catch)
it('tests a promise rejection', done => {
  promise
    .catch(error => {
      expect(error).toBe(expectedError);
    })
    .then(done);
});

Stubbing and Mocking

Jasmine provides useful helpers spyOn, spyOnProperty, jasmine.createSpy, and jasmine.createSpyObject to facilitate replacing methods with dummy placeholders, and recalling when they are called and the arguments that are passed to them. These tools should be used liberally, to test for expected behavior, to mock responses, and to block unwanted side effects (such as a method that would generate a network request or alter window.location). The documentation for these methods can be found in the Jasmine introduction page.

Sometimes you may need to spy on a method that is directly imported by another module. GitLab has a custom spyOnDependency method which utilizes babel-plugin-rewire to achieve this. It can be used like so:

// my_module.js
import { visitUrl } from '~/lib/utils/url_utility';

export default function doSomething() {
  visitUrl('/foo/bar');
}

// my_module_spec.js
import doSomething from '~/my_module';

describe('my_module', () => {
  it('does something', () => {
    const visitUrl = spyOnDependency(doSomething, 'visitUrl');

    doSomething();
    expect(visitUrl).toHaveBeenCalledWith('/foo/bar');
  });
});

Unlike spyOn, spyOnDependency expects its first parameter to be the default export of a module who's import you want to stub, rather than an object which contains a method you wish to stub (if the module does not have a default export, one is be generated by the babel plugin). The second parameter is the name of the import you wish to change. The result of the function is a Spy object which can be treated like any other Jasmine spy object.

Further documentation on the babel rewire pluign API can be found on its repository Readme doc.

Waiting in tests

Sometimes a test needs to wait for something to happen in the application before it continues. Avoid using setTimeout because it makes the reason for waiting unclear and if passed a time larger than zero it will slow down our test suite. Instead use one of the following approaches.

Promises and Ajax calls

Register handler functions to wait for the Promise to be resolved.

const askTheServer = () => {
  return axios
    .get('/endpoint')
    .then(response => {
      // do something
    })
    .catch(error => {
      // do something else
    });
};

in Jest:

it('waits for an Ajax call', () => {
  return askTheServer().then(() => {
    expect(something).toBe('done');
  });
});

in Karma:

it('waits for an Ajax call', done => {
  askTheServer()
    .then(() => {
      expect(something).toBe('done');
    })
    .then(done)
    .catch(done.fail);
});

If you are not able to register handlers to the Promise—for example because it is executed in a synchronous Vue life cycle hook—you can flush all pending Promises:

in Jest:

it('waits for an Ajax call', () => {
  synchronousFunction();
  jest.runAllTicks();

  expect(something).toBe('done');
});

in Karma:

You are out of luck. The following only works sometimes and may lead to flaky failures:

it('waits for an Ajax call', done => {
  synchronousFunction();

  // create a new Promise and hope that it resolves after the rest
  Promise.resolve()
    .then(() => {
      expect(something).toBe('done');
    })
    .then(done)
    .catch(done.fail);
});
Vue rendering

To wait until a Vue component is re-rendered, use either of the equivalent Vue.nextTick() or vm.$nextTick().

in Jest:

it('renders something', () => {
  wrapper.setProps({ value: 'new value' });

  return wrapper.vm.$nextTick().then(() => {
    expect(wrapper.text()).toBe('new value');
  });
});

in Karma:

it('renders something', done => {
  wrapper.setProps({ value: 'new value' });

  wrapper.vm
    .$nextTick()
    .then(() => {
      expect(wrapper.text()).toBe('new value');
    })
    .then(done)
    .catch(done.fail);
});
setTimeout() / setInterval() in application

If the application itself is waiting for some time, mock await the waiting. In Jest this is already done by default (see also Jest Timer Mocks). In Karma you can use the Jasmine mock clock.

const doSomethingLater = () => {
  setTimeout(() => {
    // do something
  }, 4000);
};

in Jest:

it('does something', () => {
  doSomethingLater();
  jest.runAllTimers();

  expect(something).toBe('done');
});

in Karma:

it('does something', () => {
  jasmine.clock().install();

  doSomethingLater();
  jasmine.clock().tick(4000);

  expect(something).toBe('done');
  jasmine.clock().uninstall();
});
Events

If the application triggers an event that you need to wait for in your test, register an event handler which contains the assertions:

it('waits for an event', done => {
  eventHub.$once('someEvent', eventHandler);

  someFunction();

  function eventHandler() {
    expect(something).toBe('done');
    done();
  }
});

In Jest you can also use a Promise for this:

it('waits for an event', () => {
  const eventTriggered = new Promise(resolve => eventHub.$once('someEvent', resolve));

  someFunction();

  return eventTriggered.then(() => {
    expect(something).toBe('done');
  });
});

Migrating flaky Karma tests to Jest

Some of our Karma tests are flaky because they access the properties of a shared scope. This also means that they are not easily parallelized.

Migrating flaky Karma tests to Jest will help significantly as each test is executed in an isolated scope, improving performance and predictability.

Vue.js unit tests

See this section.

Running frontend tests

For running the frontend tests, you need the following commands:

  • rake frontend:fixtures (re-)generates fixtures.
  • yarn test executes the tests.

As long as the fixtures don't change, yarn test is sufficient (and saves you some time).

Live testing and focused testing

While developing locally, it may be helpful to keep Karma running so that you can get instant feedback on as you write tests and modify code. To do this you can start Karma with yarn run karma-start. It will compile the javascript assets and run a server at http://localhost:9876/ where it will automatically run the tests on any browser which connects to it. You can enter that url on multiple browsers at once to have it run the tests on each in parallel.

While Karma is running, any changes you make will instantly trigger a recompile and retest of the entire test suite, so you can see instantly if you've broken a test with your changes. You can use Jasmine focused or excluded tests (with fdescribe or xdescribe) to get Karma to run only the tests you want while you're working on a specific feature, but make sure to remove these directives when you commit your code.

It is also possible to only run Karma on specific folders or files by filtering the run tests via the argument --filter-spec or short -f:

# Run all files
yarn karma-start
# Run specific spec files
yarn karma-start --filter-spec profile/account/components/update_username_spec.js
# Run specific spec folder
yarn karma-start --filter-spec profile/account/components/
# Run all specs which path contain vue_shared or vie
yarn karma-start -f vue_shared -f vue_mr_widget

You can also use glob syntax to match files. Remember to put quotes around the glob otherwise your shell may split it into multiple arguments:

# Run all specs named `file_spec` within the IDE subdirectory
yarn karma -f 'spec/javascripts/ide/**/file_spec.js'

RSpec feature integration tests

Information on setting up and running RSpec integration tests with Capybara can be found in the Testing Best Practices.

Frontend test fixtures

Code that is added to HAML templates (in app/views/) or makes Ajax requests to the backend has tests that require HTML or JSON from the backend. Fixtures for these tests are located at:

  • spec/frontend/fixtures/, for running tests in CE.
  • ee/spec/frontend/fixtures/, for running tests in EE.

Fixture files in:

  • The Karma test suite are served by jasmine-jquery.
  • Jest use spec/frontend/helpers/fixtures.js.

The following are examples of tests that work for both Karma and Jest:

it('makes a request', () => {
  const responseBody = getJSONFixture('some/fixture.json'); // loads spec/frontend/fixtures/some/fixture.json
  axiosMock.onGet(endpoint).reply(200, responseBody);

  myButton.click();

  // ...
});

it('uses some HTML element', () => {
  loadFixtures('some/page.html'); // loads spec/frontend/fixtures/some/page.html and adds it to the DOM

  const element = document.getElementById('#my-id');

  // ...
});

HTML and JSON fixtures are generated from backend views and controllers using RSpec (see spec/frontend/fixtures/*.rb).

For each fixture, the content of the response variable is stored in the output file. This variable gets automagically set if the test is marked as type: :request or type: :controller. Fixtures are regenerated using the bin/rake frontend:fixtures command but you can also generate them individually, for example bin/rspec spec/frontend/fixtures/merge_requests.rb. When creating a new fixture, it often makes sense to take a look at the corresponding tests for the endpoint in (ee/)spec/controllers/ or (ee/)spec/requests/.

Gotchas

RSpec errors due to JavaScript

By default RSpec unit tests will not run JavaScript in the headless browser and will simply rely on inspecting the HTML generated by rails.

If an integration test depends on JavaScript to run correctly, you need to make sure the spec is configured to enable JavaScript when the tests are run. If you don't do this you'll see vague error messages from the spec runner.

To enable a JavaScript driver in an rspec test, add :js to the individual spec or the context block containing multiple specs that need JavaScript enabled:

# For one spec
it 'presents information about abuse report', :js do
  # assertions...
end

describe "Admin::AbuseReports", :js do
  it 'presents information about abuse report' do
    # assertions...
  end
  it 'shows buttons for adding to abuse report' do
    # assertions...
  end
end

Overview of Frontend Testing Levels

Tests relevant for frontend development can be found at the following places:

All tests in spec/javascripts/ will eventually be migrated to spec/frontend/ (see also #52483).

In addition, there used to be feature tests in features/, run by Spinach. These were removed from the codebase in May 2018 (#23036).

See also Notes on testing Vue components.

Frontend unit tests

Unit tests are on the lowest abstraction level and typically test functionality that is not directly perceivable by a user.

graph RL
    plain[Plain JavaScript];
    Vue[Vue Components];
    feature-flags[Feature Flags];
    license-checks[License Checks];

    plain---Vuex;
    plain---GraphQL;
    Vue---plain;
    Vue---Vuex;
    Vue---GraphQL;
    browser---plain;
    browser---Vue;
    plain---backend;
    Vuex---backend;
    GraphQL---backend;
    Vue---backend;
    backend---database;
    backend---feature-flags;
    backend---license-checks;

    class plain tested;
    class Vuex tested;

    classDef node color:#909090,fill:#f0f0f0,stroke-width:2px,stroke:#909090
    classDef label stroke-width:0;
    classDef tested color:#000000,fill:#a0c0ff,stroke:#6666ff,stroke-width:2px,stroke-dasharray: 5, 5;

    subgraph " "
    tested;
    mocked;
    class tested tested;
    end

When to use unit tests

exported functions and classes Anything that is exported can be reused at various places in a way you have no control over. Therefore it is necessary to document the expected behavior of the public interface with tests.
Vuex actions Any Vuex action needs to work in a consistent way independent of the component it is triggered from.
Vuex mutations For complex Vuex mutations it helps to identify the source of a problem by separating the tests from other parts of the Vuex store.

When not to use unit tests

non-exported functions or classes Anything that is not exported from a module can be considered private or an implementation detail and doesn't need to be tested.
constants Testing the value of a constant would mean to copy it. This results in extra effort without additional confidence that the value is correct.
Vue components Computed properties, methods, and lifecycle hooks can be considered an implementation detail of components and don't need to be tested. They are implicitly covered by component tests. The official Vue guidelines suggest the same.

What to mock in unit tests

state of the class under test Modifying the state of the class under test directly rather than using methods of the class avoids side-effects in test setup.
other exported classes Every class needs to be tested in isolation to prevent test scenarios from growing exponentially.
single DOM elements if passed as parameters For tests that only operate on single DOM elements rather than a whole page, creating these elements is cheaper than loading a whole HTML fixture.
all server requests When running frontend unit tests, the backend may not be reachable. Therefore all outgoing requests need to be mocked.
asynchronous background operations Background operations cannot be stopped or waited on, so they will continue running in the following tests and cause side effects.

What not to mock in unit tests

non-exported functions or classes Everything that is not exported can be considered private to the module and will be implicitly tested via the exported classes / functions.
methods of the class under test By mocking methods of the class under test, the mocks will be tested and not the real methods.
utility functions (pure functions, or those that only modify parameters) If a function has no side effects because it has no state, it is safe to not mock it in tests.
full HTML pages Loading the HTML of a full page slows down tests, so it should be avoided in unit tests.

Frontend component tests

Component tests cover the state of a single component that is perceivable by a user depending on external signals such as user input, events fired from other components, or application state.

graph RL
    plain[Plain JavaScript];
    Vue[Vue Components];
    feature-flags[Feature Flags];
    license-checks[License Checks];

    plain---Vuex;
    plain---GraphQL;
    Vue---plain;
    Vue---Vuex;
    Vue---GraphQL;
    browser---plain;
    browser---Vue;
    plain---backend;
    Vuex---backend;
    GraphQL---backend;
    Vue---backend;
    backend---database;
    backend---feature-flags;
    backend---license-checks;

    class Vue tested;

    classDef node color:#909090,fill:#f0f0f0,stroke-width:2px,stroke:#909090
    classDef label stroke-width:0;
    classDef tested color:#000000,fill:#a0c0ff,stroke:#6666ff,stroke-width:2px,stroke-dasharray: 5, 5;

    subgraph " "
    tested;
    mocked;
    class tested tested;
    end

When to use component tests

  • Vue components

When not to use component tests

Vue applications Vue applications may contain many components. Testing them on a component level requires too much effort. Therefore they are tested on frontend integration level.
HAML templates HAML templates contain only Markup and no frontend-side logic. Therefore they are not complete components.

What to mock in component tests

DOM Operating on the real DOM is significantly slower than on the virtual DOM.
properties and state of the component under test Similarly to testing classes, modifying the properties directly (rather than relying on methods of the component) avoids side-effects.
Vuex store To avoid side effects and keep component tests simple, Vuex stores are replaced with mocks.
all server requests Similar to unit tests, when running component tests, the backend may not be reachable. Therefore all outgoing requests need to be mocked.
asynchronous background operations Similar to unit tests, background operations cannot be stopped or waited on, so they will continue running in the following tests and cause side effects.
child components Every component is tested individually, so child components are mocked. See also shallowMount()

What not to mock in component tests

methods or computed properties of the component under test By mocking part of the component under test, the mocks will be tested and not the real component.
functions and classes independent from Vue All plain JavaScript code is already covered by unit tests and needs not to be mocked in component tests.

Frontend integration tests

Integration tests cover the interaction between all components on a single page. Their abstraction level is comparable to how a user would interact with the UI.

graph RL
    plain[Plain JavaScript];
    Vue[Vue Components];
    feature-flags[Feature Flags];
    license-checks[License Checks];

    plain---Vuex;
    plain---GraphQL;
    Vue---plain;
    Vue---Vuex;
    Vue---GraphQL;
    browser---plain;
    browser---Vue;
    plain---backend;
    Vuex---backend;
    GraphQL---backend;
    Vue---backend;
    backend---database;
    backend---feature-flags;
    backend---license-checks;

    class plain tested;
    class Vue tested;
    class Vuex tested;
    class GraphQL tested;
    class browser tested;
    linkStyle 0,1,2,3,4,5,6 stroke:#6666ff,stroke-width:2px,stroke-dasharray: 5, 5;

    classDef node color:#909090,fill:#f0f0f0,stroke-width:2px,stroke:#909090
    classDef label stroke-width:0;
    classDef tested color:#000000,fill:#a0c0ff,stroke:#6666ff,stroke-width:2px,stroke-dasharray: 5, 5;

    subgraph " "
    tested;
    mocked;
    class tested tested;
    end

When to use integration tests

page bundles (index.js files in app/assets/javascripts/pages/) Testing the page bundles ensures the corresponding frontend components integrate well.
Vue applications outside of page bundles Testing Vue applications as a whole ensures the corresponding frontend components integrate well.

What to mock in integration tests

HAML views (use fixtures instead) Rendering HAML views requires a Rails environment including a running database which we cannot rely on in frontend tests.
all server requests Similar to unit and component tests, when running component tests, the backend may not be reachable. Therefore all outgoing requests need to be mocked.
asynchronous background operations that are not perceivable on the page Background operations that affect the page need to be tested on this level. All other background operations cannot be stopped or waited on, so they will continue running in the following tests and cause side effects.

What not to mock in integration tests

DOM Testing on the real DOM ensures our components work in the environment they are meant for. Part of this will be delegated to cross-browser testing.
properties or state of components On this level, all tests can only perform actions a user would do. For example to change the state of a component, a click event would be fired.
Vuex stores When testing the frontend code of a page as a whole, the interaction between Vue components and Vuex stores is covered as well.

Feature tests

In contrast to frontend integration tests, feature tests make requests against the real backend instead of using fixtures. This also implies that database queries are executed which makes this category significantly slower.

See also the RSpec testing guidelines.

graph RL
    plain[Plain JavaScript];
    Vue[Vue Components];
    feature-flags[Feature Flags];
    license-checks[License Checks];

    plain---Vuex;
    plain---GraphQL;
    Vue---plain;
    Vue---Vuex;
    Vue---GraphQL;
    browser---plain;
    browser---Vue;
    plain---backend;
    Vuex---backend;
    GraphQL---backend;
    Vue---backend;
    backend---database;
    backend---feature-flags;
    backend---license-checks;

    class backend tested;
    class plain tested;
    class Vue tested;
    class Vuex tested;
    class GraphQL tested;
    class browser tested;
    linkStyle 0,1,2,3,4,5,6,7,8,9,10 stroke:#6666ff,stroke-width:2px,stroke-dasharray: 5, 5;

    classDef node color:#909090,fill:#f0f0f0,stroke-width:2px,stroke:#909090
    classDef label stroke-width:0;
    classDef tested color:#000000,fill:#a0c0ff,stroke:#6666ff,stroke-width:2px,stroke-dasharray: 5, 5;

    subgraph " "
    tested;
    mocked;
    class tested tested;
    end

When to use feature tests

  • Use cases that require a backend and cannot be tested using fixtures.
  • Behavior that is not part of a page bundle but defined globally.

Relevant notes

A :js flag is added to the test to make sure the full environment is loaded.

scenario 'successfully', :js do
  sign_in(create(:admin))
end

The steps of each test are written using capybara methods (documentation).

Bear in mind XHR calls might require you to use wait_for_requests in between steps, like so:

find('.form-control').native.send_keys(:enter)

wait_for_requests

expect(page).not_to have_selector('.card')

Test helpers

Vuex Helper: testAction

We have a helper available to make testing actions easier, as per official documentation:

testAction(
  actions.actionName, // action
  { }, // params to be passed to action
  state, // state
  [
    { type: types.MUTATION},
    { type: types.MUTATION_1, payload: {}},
  ], // mutations committed
  [
    { type: 'actionName', payload: {}},
    { type: 'actionName1', payload: {}},
  ] // actions dispatched
  done,
);

Check an example in spec/javascripts/ide/stores/actions_spec.jsspec/javascripts/ide/stores/actions_spec.js.

Vue Helper: mountComponent

To make mounting a Vue component easier and more readable, we have a few helpers available in spec/helpers/vue_mount_component_helper:

  • createComponentWithStore
  • mountComponentWithStore

Examples of usage:

beforeEach(() => {
  vm = createComponentWithStore(Component, store);

  vm.$store.state.currentBranchId = 'master';

  vm.$mount();
});

beforeEach(() => {
  vm = mountComponentWithStore(Component, {
    el: '#dummy-element',
    store,
    props: { badge },
  });
});

Don't forget to clean up:

afterEach(() => {
  vm.$destroy();
});

Testing with older browsers

Some regressions only affect a specific browser version. We can install and test in particular browsers with either Firefox or Browserstack using the following steps:

Browserstack

Browserstack allows you to test more than 1200 mobile devices and browsers. You can use it directly through the live app or you can install the chrome extension for easy access. You can find the credentials on 1Password, under frontendteam@gitlab.com.

Firefox

macOS

You can download any older version of Firefox from the releases FTP server, https://ftp.mozilla.org/pub/firefox/releases/:

  1. From the website, select a version, in this case 50.0.1.
  2. Go to the mac folder.
  3. Select your preferred language, you will find the dmg package inside, download it.
  4. Drag and drop the application to any other folder but the Applications folder.
  5. Rename the application to something like Firefox_Old.
  6. Move the application to the Applications folder.
  7. Open up a terminal and run /Applications/Firefox_Old.app/Contents/MacOS/firefox-bin -profilemanager to create a new profile specific to that Firefox version.
  8. Once the profile has been created, quit the app, and run it again like normal. You now have a working older Firefox version.

Return to Testing documentation