Examine individual changes
This page allows you to examine the variables generated by the Edit Filter for an individual change.
Variables generated for this change
| Variable | Value |
|---|---|
Edit count of the user (user_editcount) | 15 |
Name of the user account (user_name) | 'Screen.tester' |
Age of the user account (user_age) | 255149 |
Groups (including implicit) the user is in (user_groups) | [
0 => '*',
1 => 'user'
] |
Global groups that the user is in (global_user_groups) | [] |
Whether or not a user is editing through the mobile interface (user_mobile) | false |
Page ID (page_id) | 0 |
Page namespace (page_namespace) | 0 |
Page title without namespace (page_title) | 'Automated UI testing with Screenster' |
Full page title (page_prefixedtitle) | 'Automated UI testing with Screenster' |
Last ten users to contribute to the page (page_recent_contributors) | '' |
First user to contribute to the page (page_first_contributor) | '' |
Action (action) | 'edit' |
Edit summary/reason (summary) | 'Added description and images' |
Whether or not the edit is marked as minor (no longer in use) (minor_edit) | false |
Old page wikitext, before the edit (old_wikitext) | '' |
New page wikitext, after the edit (new_wikitext) | '
== UI testing automation ==
The problem of automation of QA activities becomes increasingly important as complexity and variety of [[software]] products grow fast, on a global scale.
== What is Screenster ==
== How it works ==
[[File:Baseline created.png|thumb|400x400px]]
=== 1. Record Visual Baseline ===
As you interact with a web page Screenster records your actions. Unlike other recorders, it captures a screenshot for each step and stores it as a baseline. As soon as you are done recording, you are practically done automating. No coding, no element ids, no adding checks and assertions.
=== 2. Configure Dynamic Areas ===
Rerun recorded test. If differences are detected between the baseline and regression run screenshots, they are highlighted on the screen. Tell Screenster to ignore the dynamic portions of the UI from future comparison and you are ready to run this test in CI.
[[File:Finding differences.png|thumb|400x400px]]
=== 3. Manage Differences ===
Screenster can run tests as part of CI. If a difference is detected between the baseline and a regression run, the test is marked as failed. After a review the tester can approve changes to the baseline or report them as a bug.
== Important Features ==
=== Automatic Date/Time Management ===
Since date and time often change on the page, Screenster recognizes dates and does not flag differences in dates between the run and the baseline if dates are considered “consistent”.
If the difference between the date/time on the page screenshot and date/time of the run the same as the difference between the date/time of the baseline screenshot and the date/time of the baseline run then this difference is ignored.
== Installation ==
Screenster runs on a server and is accessed by users through any web browser. Currently Screenster server runs only on Windows because it needs to support Internet Explorer. It is better to install Screenster on a standalone server or a VM that is part of your CI environment.
Download and run Screenster setup. It will add Windows service Screenster that should autostart with the server. Make sure that Firefox and Chrome are installed and accessible to all users.
=== System requirements ===
Operating system: Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2016
Memory: 2 GB RAM
Video display: 1024 x 768
Disk Space: 5 GB' |
Unified diff of changes made by edit (edit_diff) | '@@ -1,2 +1,39 @@
+== UI testing automation ==
+
+The problem of automation of QA activities becomes increasingly important as complexity and variety of [[software]] products grow fast, on a global scale.
+
+== What is Screenster ==
+
+== How it works ==
+[[File:Baseline created.png|thumb|400x400px]]
+
+=== 1. Record Visual Baseline ===
+
+As you interact with a web page Screenster records your actions. Unlike other recorders, it captures a screenshot for each step and stores it as a baseline. As soon as you are done recording, you are practically done automating. No coding, no element ids, no adding checks and assertions.
+
+=== 2. Configure Dynamic Areas ===
+
+Rerun recorded test. If differences are detected between the baseline and regression run screenshots, they are highlighted on the screen. Tell Screenster to ignore the dynamic portions of the UI from future comparison and you are ready to run this test in CI.
+[[File:Finding differences.png|thumb|400x400px]]
+
+=== 3. Manage Differences ===
+
+Screenster can run tests as part of CI. If a difference is detected between the baseline and a regression run, the test is marked as failed. After a review the tester can approve changes to the baseline or report them as a bug.
+
+== Important Features ==
+
+=== Automatic Date/Time Management ===
+Since date and time often change on the page, Screenster recognizes dates and does not flag differences in dates between the run and the baseline if dates are considered “consistent”.
+If the difference between the date/time on the page screenshot and date/time of the run the same as the difference between the date/time of the baseline screenshot and the date/time of the baseline run then this difference is ignored.
+
+== Installation ==
+Screenster runs on a server and is accessed by users through any web browser. Currently Screenster server runs only on Windows because it needs to support Internet Explorer. It is better to install Screenster on a standalone server or a VM that is part of your CI environment.
+Download and run Screenster setup. It will add Windows service Screenster that should autostart with the server. Make sure that Firefox and Chrome are installed and accessible to all users.
+
+=== System requirements ===
+Operating system: Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2016
+Memory: 2 GB RAM
+Video display: 1024 x 768
+Disk Space: 5 GB
' |
New page size (new_size) | 2370 |
Old page size (old_size) | 0 |
Size change in edit (edit_delta) | 2370 |
Lines added in edit (added_lines) | [
0 => '== UI testing automation ==',
1 => false,
2 => 'The problem of automation of QA activities becomes increasingly important as complexity and variety of [[software]] products grow fast, on a global scale.',
3 => false,
4 => '== What is Screenster ==',
5 => false,
6 => '== How it works ==',
7 => '[[File:Baseline created.png|thumb|400x400px]]',
8 => false,
9 => '=== 1. Record Visual Baseline ===',
10 => false,
11 => 'As you interact with a web page Screenster records your actions. Unlike other recorders, it captures a screenshot for each step and stores it as a baseline. As soon as you are done recording, you are practically done automating. No coding, no element ids, no adding checks and assertions. ',
12 => false,
13 => '=== 2. Configure Dynamic Areas ===',
14 => false,
15 => 'Rerun recorded test. If differences are detected between the baseline and regression run screenshots, they are highlighted on the screen. Tell Screenster to ignore the dynamic portions of the UI from future comparison and you are ready to run this test in CI. ',
16 => '[[File:Finding differences.png|thumb|400x400px]]',
17 => false,
18 => '=== 3. Manage Differences ===',
19 => false,
20 => 'Screenster can run tests as part of CI. If a difference is detected between the baseline and a regression run, the test is marked as failed. After a review the tester can approve changes to the baseline or report them as a bug.',
21 => false,
22 => '== Important Features ==',
23 => false,
24 => '=== Automatic Date/Time Management ===',
25 => 'Since date and time often change on the page, Screenster recognizes dates and does not flag differences in dates between the run and the baseline if dates are considered “consistent”.',
26 => 'If the difference between the date/time on the page screenshot and date/time of the run the same as the difference between the date/time of the baseline screenshot and the date/time of the baseline run then this difference is ignored.',
27 => false,
28 => '== Installation ==',
29 => 'Screenster runs on a server and is accessed by users through any web browser. Currently Screenster server runs only on Windows because it needs to support Internet Explorer. It is better to install Screenster on a standalone server or a VM that is part of your CI environment.',
30 => 'Download and run Screenster setup. It will add Windows service Screenster that should autostart with the server. Make sure that Firefox and Chrome are installed and accessible to all users. ',
31 => false,
32 => '=== System requirements ===',
33 => 'Operating system: Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2016',
34 => 'Memory: 2 GB RAM',
35 => 'Video display: 1024 x 768',
36 => 'Disk Space: 5 GB'
] |
Lines removed in edit (removed_lines) | [] |
External links added in the edit (added_links) | [] |
External links in the page, before the edit (old_links) | [] |
Parsed HTML source of the new revision (new_html) | '<p></p>
<div id="toc" class="toc">
<div id="toctitle">
<h2>Contents</h2>
</div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#UI_testing_automation"><span class="tocnumber">1</span> <span class="toctext">UI testing automation</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#What_is_Screenster"><span class="tocnumber">2</span> <span class="toctext">What is Screenster</span></a></li>
<li class="toclevel-1 tocsection-3"><a href="#How_it_works"><span class="tocnumber">3</span> <span class="toctext">How it works</span></a>
<ul>
<li class="toclevel-2 tocsection-4"><a href="#1._Record_Visual_Baseline"><span class="tocnumber">3.1</span> <span class="toctext">1. Record Visual Baseline</span></a></li>
<li class="toclevel-2 tocsection-5"><a href="#2._Configure_Dynamic_Areas"><span class="tocnumber">3.2</span> <span class="toctext">2. Configure Dynamic Areas</span></a></li>
<li class="toclevel-2 tocsection-6"><a href="#3._Manage_Differences"><span class="tocnumber">3.3</span> <span class="toctext">3. Manage Differences</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-7"><a href="#Important_Features"><span class="tocnumber">4</span> <span class="toctext">Important Features</span></a>
<ul>
<li class="toclevel-2 tocsection-8"><a href="#Automatic_Date.2FTime_Management"><span class="tocnumber">4.1</span> <span class="toctext">Automatic Date/Time Management</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-9"><a href="#Installation"><span class="tocnumber">5</span> <span class="toctext">Installation</span></a>
<ul>
<li class="toclevel-2 tocsection-10"><a href="#System_requirements"><span class="tocnumber">5.1</span> <span class="toctext">System requirements</span></a></li>
</ul>
</li>
</ul>
</div>
<p></p>
<h2><span class="mw-headline" id="UI_testing_automation">UI testing automation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=1" title="Edit section: UI testing automation">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>The problem of automation of QA activities becomes increasingly important as complexity and variety of <a href="/wiki/Software" title="Software">software</a> products grow fast, on a global scale.</p>
<h2><span class="mw-headline" id="What_is_Screenster">What is Screenster</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=2" title="Edit section: What is Screenster">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<h2><span class="mw-headline" id="How_it_works">How it works</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=3" title="Edit section: How it works">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<div class="thumb tright">
<div class="thumbinner" style="width:402px;"><a href="/wiki/File:Baseline_created.png" class="image"><img alt="Baseline created.png" src="//upload.wikimedia.org/wikipedia/commons/thumb/5/51/Baseline_created.png/400px-Baseline_created.png" width="400" height="265" class="thumbimage" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/5/51/Baseline_created.png/600px-Baseline_created.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/5/51/Baseline_created.png/800px-Baseline_created.png 2x" data-file-width="1324" data-file-height="877" /></a>
<div class="thumbcaption">
<div class="magnify"><a href="/wiki/File:Baseline_created.png" class="internal" title="Enlarge"></a></div>
</div>
</div>
</div>
<h3><span class="mw-headline" id="1._Record_Visual_Baseline">1. Record Visual Baseline</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=4" title="Edit section: 1. Record Visual Baseline">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>As you interact with a web page Screenster records your actions. Unlike other recorders, it captures a screenshot for each step and stores it as a baseline. As soon as you are done recording, you are practically done automating. No coding, no element ids, no adding checks and assertions.</p>
<h3><span class="mw-headline" id="2._Configure_Dynamic_Areas">2. Configure Dynamic Areas</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=5" title="Edit section: 2. Configure Dynamic Areas">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Rerun recorded test. If differences are detected between the baseline and regression run screenshots, they are highlighted on the screen. Tell Screenster to ignore the dynamic portions of the UI from future comparison and you are ready to run this test in CI.</p>
<div class="thumb tright">
<div class="thumbinner" style="width:402px;"><a href="/wiki/File:Finding_differences.png" class="image"><img alt="Finding differences.png" src="//upload.wikimedia.org/wikipedia/commons/thumb/5/58/Finding_differences.png/400px-Finding_differences.png" width="400" height="268" class="thumbimage" srcset="//upload.wikimedia.org/wikipedia/commons/thumb/5/58/Finding_differences.png/600px-Finding_differences.png 1.5x, //upload.wikimedia.org/wikipedia/commons/thumb/5/58/Finding_differences.png/800px-Finding_differences.png 2x" data-file-width="1308" data-file-height="876" /></a>
<div class="thumbcaption">
<div class="magnify"><a href="/wiki/File:Finding_differences.png" class="internal" title="Enlarge"></a></div>
</div>
</div>
</div>
<h3><span class="mw-headline" id="3._Manage_Differences">3. Manage Differences</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=6" title="Edit section: 3. Manage Differences">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Screenster can run tests as part of CI. If a difference is detected between the baseline and a regression run, the test is marked as failed. After a review the tester can approve changes to the baseline or report them as a bug.</p>
<h2><span class="mw-headline" id="Important_Features">Important Features</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=7" title="Edit section: Important Features">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<h3><span class="mw-headline" id="Automatic_Date.2FTime_Management">Automatic Date/Time Management</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=8" title="Edit section: Automatic Date/Time Management">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Since date and time often change on the page, Screenster recognizes dates and does not flag differences in dates between the run and the baseline if dates are considered “consistent”. If the difference between the date/time on the page screenshot and date/time of the run the same as the difference between the date/time of the baseline screenshot and the date/time of the baseline run then this difference is ignored.</p>
<h2><span class="mw-headline" id="Installation">Installation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=9" title="Edit section: Installation">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Screenster runs on a server and is accessed by users through any web browser. Currently Screenster server runs only on Windows because it needs to support Internet Explorer. It is better to install Screenster on a standalone server or a VM that is part of your CI environment. Download and run Screenster setup. It will add Windows service Screenster that should autostart with the server. Make sure that Firefox and Chrome are installed and accessible to all users.</p>
<h3><span class="mw-headline" id="System_requirements">System requirements</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/w/index.php?title=Automated_UI_testing_with_Screenster&action=edit&section=10" title="Edit section: System requirements">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Operating system: Windows 8, Windows 8.1, Windows 10, Windows Server 2012, Windows Server 2016 Memory: 2 GB RAM Video display: 1024 x 768 Disk Space: 5 GB</p>
<!--
NewPP limit report
Parsed by mw1137
Cached time: 20160610144250
Cache expiry: 2592000
Dynamic content: false
CPU time usage: 0.007 seconds
Real time usage: 0.013 seconds
Preprocessor visited node count: 56/1000000
Preprocessor generated node count: 0/1500000
Post‐expand include size: 0/2097152 bytes
Template argument size: 0/2097152 bytes
Highest expansion depth: 2/40
Expensive parser function count: 0/500
Number of Wikibase entities loaded: 0-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00% 0.000 1 - -total
-->
' |
Whether or not the change was made through a Tor exit node (tor_exit_node) | 0 |
Unix timestamp of change (timestamp) | 1465569770 |
External links in the new text (new_links) | [] |