Skip to content
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.

An example application showing how to bootstrap functional tests with Sencha products

Notifications You must be signed in to change notification settings

ModusCreateOrg/senchaTestStarterApp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

No longer maintained

[DEPRECATED] This repository is no longer maintained

While this project is fully functional, the dependencies are no longer up to date. You are still welcome to explore, learn, and use the code provided here.

Modus is dedicated to supporting the community with innovative ideas, best-practice patterns, and inspiring open source solutions. Check out the latest Modus Labs projects.

Modus Labs


E2E && Integration tests

Install requirements using the following commands:

change dir to '/test/e2e/' change dir to '/test/integration/'

  • Follow the installation steps for Sencha Studio and STC:
  • http://docs.sencha.com/sencha_test/guides/sencha_test_installation.html
  • Make sure you have node > 4.2.1. You can use nvm: https://www.npmjs.com/package/nvm
  • E2E tests Configuration:
  • Install Selenium Standalone Server:
  • cd tests/e2e
  • ./install.sh
  • If no permissions to run then chmod +x install.sh and run again.
  • Start Selenium Standalone Server:
  • ./start.sh
  • Integration tests Configuration:
  • Install Selenium Standalone Server:
  • cd tests/integration
  • ./install.sh
  • If no permissions to run then chmod +x install.sh and run again.
  • Start Selenium Standalone Server:
  • ./start.sh

Run the tests with STC

change dir to '/test/e2e/' change dir to '/test/integration/'

  • To run all tests in /tests, run in terminal:
  • ./run-tests-chrome.sh
  • ./run-tests.sh
  • To run tests from different scopes and other browsers:
  • stc run -o output -p pool -s scenario
  • o - Output format. Supported values are text, teamcity and junit
  • p - Name of the pool from whence tests will be executed. This must be a pool associated with a browser farm
  • s - Path to the scenario to be executed. If unspecified, defaults to the current directory.
  • More info at http://docs.sencha.com/sencha_test/guides/command_line_archive_server.html
  • eg: stc run -p "firefox" -s tests/ui-tests

Performance tests

Tests are using a version of jMeter 3.0 with custom plugins

Install requirements

  • install java JDK and add to path
  • unzip test/performance/apache_jmeter_3.0.zip
  • open bin/jmeter.exec and edit the following (if not already edited):
line 91 to: HEAP="-Xms2048m -Xmx2048m"
line 96 to: NEW="-XX:NewSize=512m -XX:MaxNewSize=512m"

Run the tests

  • File > Open > [choose PerformanceTests.jmx]
  • under jMeter Users Thread Group change:
Number of Threads to desired value: Default = 10
Loop Count to desired value: Default = 10
  • this means 10 concurrent users for 10 times
  • Run > Start

Inspect the results

There are 4 listeners at the end of the Thread Group that provide useful info.

About

An example application showing how to bootstrap functional tests with Sencha products

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published