#Test::CPAN::Changes | Explore Tumblr posts and blogs

globalmediacampaign · 5 years ago

Text

Migrating legacy PostgreSQL databases to Amazon RDS or Aurora PostgreSQL using Bucardo

If you are using PostgreSQL earlier than 9.4, you are using an unsupported version of PostgreSQL, and may have limited options to migrate or replicate your databases in Amazon RDS or Amazon Aurora PostgreSQL. This is primarily because PostgreSQL versions older than 9.4 can’t perform logical replication. Bucardo is an open-source utility that can replicate data changes asynchronously to multiple secondary or multiple masters. It is a trigger-based replication and proven to be consistent and stable for more extensive migrations and ongoing replications. Bucardo can perform full load for tables without a primary key. However, to replicate delta data changes from Primary, create a primary key before you start the setup. This post demonstrates how to set up Bucardo and replicate data changes from PostgreSQL 8.4 to PostgreSQL 9.6. Prerequisites Before getting started, you must have the following: One EC2 instance with Ubuntu 16.04 for Bucardo (Bucardo Server: 172.31.88.4) One EC2 instance with RHEL 6 with PostgreSQL 8.4.2 (PostgreSQL 8.4.2: 172.31.16.177) One RDS PostgreSQL 9.6 in us-east-1 (RDS 9.6) This post uses PostgreSQL 8.4.2 on Amazon EC2; however, the PostgreSQL database might be running on-premises. This solution installs Bucardo 5.4.1 on Ubuntu 16.04, which means that the repository for Bucardo is on the same host running on a PostgreSQL 9.6 instance. The following diagram shows the architecture of the data replication flow. Fig: Replication Architecture to migrate PostgreSQL 8.4 to RDS PostgreSQL 9.6 using Bucardo. Installing Bucardo binaries There are several packages that you must install before installing Bucardo. See the following code: #apt-get install postgresql-plperl-9.6 libdbd-pg-perl libboolean-perl build-essential libdbd-mock-perl libdbd-pg-perl libanyevent-dbd-pg-perl libpg-hstore-perl libpgobject-perl Connect to CPAN and install DBI,DBD::Pg,DBIx::Safe. See the following code: cpan > install DBI cpan > install DBD::Pg cpan > install DBIx::Safe Download the Bucardo binaries into your local directory and untar. See the following code: $wget http://bucardo.org/downloads/Bucardo-5.4.1.tar.gz tar xvfz Bucardo-5.4.1.tar.gz $perl Makefile.PL $sudo make install Creating superusers and the repository database You must create a Bucardo superuser and repository database to control and track the replications between environments. Connect to DB-APP1 using the PSQL client or pgadmin4 and create the superuser and repository on DR-App1. See the following code: postgres=# create user bucardo superuser; CREATE ROLE postgres=# create database bucardo; CREATE DATABASE postgres=# du List of roles Role name | Attributes | Member of -----------+------------------------------------------------------------+----------- bucardo | Superuser | {} postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {} replica | Replication | {} postgres=# alter database bucardo owner to bucardo; ALTER DATABASE postgres=# list List of databases Name | Owner | Encoding | Collate | Ctype | Access privileges -----------+----------+----------+-------------+-------------+----------------------- bucardo | bucardo | UTF8 | en_US.UTF-8 | en_US.UTF-8 | postgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | template0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres template1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c/postgres + | | | | | postgres=CTc/postgres (4 rows) After you create the superuser and repository database, exit from PSQL and run “bucardo install” from the terminal where Bucardo software is staged. This creates a set of tables in the Bucardo database (the database owner should be a Bucardo superuser). Installing the Bucardo repository To install the Bucardo repository, enter the following code: postgres@ip-172-31-88-4:~/Bucardo-5.4.1$ sudo bucardo install This installs the Bucardo database into an existing PostgreSQL cluster. You must have compiled PostgreSQL with Perl support, and connect as a superuser. See the following code: Current connection settings: 1. Host: 2. Port: 5432 3. User: postgres 4. Database: bucardo 5. PID directory: /var/run/bucardo Enter a number to change it, P to proceed, or Q to quit: p Postgres version is: 9.6 Attempting to create and populate the bucardo database and schema Database creation is complete Updated configuration setting "piddir" Installation is now complete. If you see errors or need help, you can contact Bucardo support for assistance at [email protected]. You may want to check over the configuration variables next. See the following code: bucardo show all Change any setting by using: bucardo set foo=bar postgres@ip-172-31-88-4:~/Bucardo-5.4.1$ Whitelisting Bucardo and the PostgreSQL database server to connect with each other Use pgpass to set up passwordless authentication to connect the source and target databases securely. On the Bucardo server, enter the following code: postgres@ip-172-31-88-4:~$ touch ~/.pgpass postgres@ip-172-31-88-4:~$ chmod 0600 ~/.pgpass postgres@ip-172-31-88-4:~$ cat ~/.pgpass #server:port:database:username:password 127.0.0.1:5432:postgres:postgres:XXXXXX 172.31.88.4:5432:bucardo:postgres:XXXXXX 172.31.16.177:5432:repdb:postgres:XXXXXX pgrds.cxad2e11vriv.us-east-1.rds.amazonaws.com:5432:repdb:postgres:XXXXXX Verify that the Bucardo server can connect the source and target databases without a password with the following code: postgres@ip-172-31-88-4:~$ psql -h 172.31.16.177 -d repdb -U postgres -w -c "select count(*) from pgbench_branches" count ------- 1 (1 row) postgres@ip-172-31-88-4:~$ psql --host 'pgrds.cxad2e11vriv.us-east-1.rds.amazonaws.com' --port 5432 --username 'postgres' 'repdb' -w -c "select count(*) from pgbench_branches" count ------- 1 (1 row) Resolving a permission denied error Because RDS is a managed service, AWS doesn’t provide superuser privileges for security reasons. To perform a trigger-based replication, you must enable the parameter session_replication_role. You can use the security definer function rds_session_replication_role, which helps you to set the parameter to replica when an event occurs. To be consistent across all environments, this post creates the security definer function in EC2 PostgreSQL (8.4.2) and RDS. Create language plpgsql; with the following code: CREATE OR REPLACE FUNCTION public.rds_session_replication_role(role text) RETURNS text LANGUAGE plpgsql SECURITY DEFINER AS $function$ DECLARE curr_val text := 'unset'; BEGIN EXECUTE 'SET session_replication_role = ' || quote_literal(role); EXECUTE 'SHOW session_replication_role' INTO curr_val; RETURN curr_val; END $function$; postgres=> revoke all on function rds_session_replication_role(text) from public; REVOKE postgres=> grant execute on function rds_session_replication_role(text) to rds_superuser; GRANT postgres=> grant rds_superuser to postgres; GRANT Also, make changes to the bucardo.pm file at lines 5397 and 5330 with the following code: $dbh->do(q{select rds_session_replication_role('replica');}); ## Assumes a sane default ! From. $dbh->do(q{SET session_replication_role = default}); ## Assumes a sane default ! Alternatively, you can download the updated bucardo.pm file and move the file to the server where Bucardo is running under the location /usr/local/share/perl/5.22.1/Bucardo.pm. If you are running in production, please test it before using it. Generating a sample source database and initiating target full load On the source database, generate some test data using pgbench. This post generates four tables, three with the primary key enabled and one without the primary key enabled. See the following code: postgres=# create database repdb; CREATE DATABASE The following code is the generated sample data in repdb: [postgres@ip-172-31-16-177 ~]$ pgbench -i repdb NOTICE: table "pgbench_branches" does not exist, skipping NOTICE: table "pgbench_tellers" does not exist, skipping NOTICE: table "pgbench_accounts" does not exist, skipping NOTICE: table "pgbench_history" does not exist, skipping creating tables... 10000 tuples done. 20000 tuples done. 30000 tuples done. 40000 tuples done. 50000 tuples done. 60000 tuples done. 70000 tuples done. 80000 tuples done. 90000 tuples done. 100000 tuples done. set primary key... NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "pgbench_branches_pkey" for table "pgbench_branches" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "pgbench_tellers_pkey" for table "pgbench_tellers" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "pgbench_accounts_pkey" for table "pgbench_accounts" vacuum...done. Verify the data count and table structures. See the following code: repdb=# select count(*) from pgbench_accounts; 100000 repdb=# select count(*) from pgbench_branches; 1 repdb=# select count(*) from pgbench_history; 0 repdb=# select count(*) from pgbench_tellers; 10 Migrating repdb from the source database using pg_dump and pg_restore Back up the source database using pg_dump. See the following code: postgres@ip-172-31-88-4:~$ pg_dump -Fc -v -h ec2-34-229-97-46.compute-1.amazonaws.com -U postgres repdb -w > repdb_bkp1.dump pg_dump: last built-in OID is 16383 pg_dump: reading extensions pg_dump: identifying extension members …… Log in to RDS PostgreSQL and create the database repdb. See the following code: postgres@ip-172-31-88-4:~$ psql --host 'pgrds.cxad2e11vriv.us-east-1.rds.amazonaws.com' --port 5432 --username 'postgres' 'postgres' Password for user postgres: psql (9.6.15) SSL connection (protocol: TLSv1.2, cipher: ECDHE-RSA-AES256-GCM-SHA384, bits: 256, compression: off) Type "help" for help. postgres=> create database repdb; CREATE DATABASE Restore the dump file generated in the newly created repdb in RDS PostgreSQL using pg_restore. See the following code: postgres@ip-172-31-88-4:~$ pg_restore -v -h pgrds.cxad2e11vriv.us-east-1.rds.amazonaws.com -U postgres -d repdb repdb_bkp1.dump pg_restore: connecting to database for restore Password: pg_restore: creating SCHEMA "public" pg_restore: creating COMMENT "SCHEMA public" pg_restore: creating PROCEDURAL LANGUAGE "plpgsql" For more information, see Importing Data into PostgreSQL on Amazon RDS. Configuring Bucardo to replicate tables with a primary key A typical Bucardo setup consists of steps to add the source and target databases, add tables with a primary key to the group, and create and enable the sync to start replicating the changes from source. To add the source database, enter the following code: postgres@ip-172-31-88-4:~$ bucardo add db pgdb84 dbhost=ec2-34-229-97-46.compute-1.amazonaws.com dbport=5432 dbname=repdb dbuser=postgres Added database "pgdb84" To add the target RDS database, enter the following code: postgres@ip-172-31-88-4:~$ bucardo add db rds96 dbhost=pgrds.cxad2e11vriv.us-east-1.rds.amazonaws.com dbport=5432 dbname=repdb dbuser=postgres dbpass=postgres123 Added database "rds96" To add tables to the herd, enter the following code: postgres@ip-172-31-88-4:~$ bucardo add table pgbench_accounts pgbench_branches pgbench_tellers herd=herd_pg84 db=pgdb84 Created the relgroup named "herd_pg84" The following tables or sequences are now part of the relgroup "herd_pg84": public.pgbench_accounts public.pgbench_branches public.pgbench_tellers To add the database group, enter the following code: postgres@ip-172-31-88-4:~$ bucardo add dbgroup pgdb84_to_rds96 pgdb84:source rds96:target Created dbgroup "pgdb84_to_rds96" Added database "pgdb84" to dbgroup "pgdb84_to_rds96" as source Added database "rds96" to dbgroup "pgdb84_to_rds96" as target postgres@ip-172-31-88-4:~$ bucardo add sync sync_pg84_rds96 relgroup=herd_pg84 db=pgdb84,rds96 Added sync "sync_pg84_rds96" Using existing dbgroup "dbgrp84_96" You can have multiple databases in a particular database group. Check the Bucardo sync status before you start to make sure that you see the parameters created. See the following code: postgres@ip-172-31-88-4:~$ sudo bucardo status sync_pg84_rds96 [sudo] password for postgres: ====================================================================== Sync name : sync_pg84_rds96 Current state : No records found Source relgroup/database : herd_pg84 / pgdb84 Tables in sync : 3 Status : Active Check time : None Overdue time : 00:00:00 Expired time : 00:00:00 Stayalive/Kidsalive : Yes / Yes Rebuild index : No Autokick : Yes Onetimecopy : No Post-copy analyze : Yes Last error: : ====================================================================== Start Bucardo and verify its status. See the following code: postgres@ip-172-31-88-4:~$ sudo bucardo start Checking for existing processes Removing file "/var/run/bucardo/fullstopbucardo" Starting Bucardo postgres@ip-172-31-88-4:~$ sudo bucardo status sync_pg84_rds96 ====================================================================== Last good : Dec 05, 2019 08:30:03 (time to run: 1s) Rows deleted/inserted : 0 / 0 Sync name : sync_pg84_rds96 Current state : Good Source relgroup/database : herd_pg84 / pgdb84 Tables in sync : 3 Status : Active Check time : None Overdue time : 00:00:00 Expired time : 00:00:00 Stayalive/Kidsalive : Yes / Yes Rebuild index : No Autokick : Yes Onetimecopy : No Post-copy analyze : Yes Last error: : ====================================================================== The Current State is Good and no inserts, updates, and deletes are happening currently in the source database. To test the replication, generate a test load in the source database using pgbench and monitor changes on the target. See the following code: [postgres@ip-172-31-16-177 ~]$ pgbench -t 10000 repdb starting vacuum...end. transaction type: TPC-B (sort of) scaling factor: 1 query mode: simple number of clients: 1 number of transactions per client: 10000 number of transactions actually processed: 10000/10000 tps = 503.183795 (including connections establishing) tps = 503.244214 (excluding connections establishing) After you run pgbench, it generates some transactions, but Bucardo can’t move to the target due to a permission issue. Therefore, the status of Current State is Bad. See the following code: postgres@ip-172-31-88-4:~$ sudo bucardo status sync_pg84_rds96 ====================================================================== Last bad : Dec 05, 2019 08:32:54 (time until fail: 1s) Sync name : sync_pg84_rds96 Current state : Bad Source relgroup/database : herd_pg84 / pgdb84 Tables in sync : 3 Status : Active Check time : None Overdue time : 00:00:00 Expired time : 00:00:00 Stayalive/Kidsalive : Yes / Yes Rebuild index : No Autokick : Yes Onetimecopy : No Post-copy analyze : Yes Last error: : Failed : DBD::Pg::db do failed: ERROR: function rds_session_replication_role(unknown) does not exist LINE 1: select rds_session_replication_role('replica'); ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. at /usr/local/share/perl/5.22.1/Bucardo.pm line 5328. Line: 5041 Main DB state: ? Error: none DB pgdb84 state: ? Error: none DB rds96 state: 42883 Error: 7 (KID 14864) ====================================================================== If you encounter this error, follow the steps to resolve a permission denied error. In this example, security definer functions were not created in source and target databases and caused the preceding error. After implementing the security definer, restart Bucardo. See the following code: postgres@ip-172-31-88-4:~$ sudo bucardo restart Creating /var/run/bucardo/fullstopbucardo ... Done Checking for existing processes Removing file "/var/run/bucardo/fullstopbucardo" Starting Bucardo The Current State is now Good, and 294 deletes and inserts happened in the database. This confirms that your Bucardo is healthy. You can ignore the entry for Last error. See the following code: postgres@ip-172-31-88-4:~$ sudo bucardo status sync_pg84_rds96 ====================================================================== Last good : Dec 05, 2019 08:51:21 (time to run: 1s) Rows deleted/inserted : 294 / 294 Last bad : Dec 05, 2019 08:35:06 (time until fail: 1s) Sync name : sync_pg84_rds96 Current state : Good Source relgroup/database : herd_pg84 / pgdb84 Tables in sync : 3 Status : Active Check time : None Overdue time : 00:00:00 Expired time : 00:00:00 Stayalive/Kidsalive : Yes / Yes Rebuild index : No Autokick : Yes Onetimecopy : No Post-copy analyze : Yes Last error: : Failed : DBD::Pg::db do failed: ERROR: function rds_session_replication_role(unknown) does not exist LINE 1: select rds_session_replication_role('replica'); ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. at /usr/local/share/perl/5.22.1/Bucardo.pm line 5328. Line: 5041 Main DB state: ? Error: none DB pgdb84 state: ? Error: none DB rds96 state: 42883 Error: 7 (KID 15006) ====================================================================== To debug the replication, Bucardo logs are located in the /var/log directory. See the following code: postgres@ip-172-31-88-4:~$ tail -f /var/log/bucardo/log.bucardo (15337) [Thu Dec 5 08:51:25 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_tellers : 10 (15337) [Thu Dec 5 08:51:25 2019] KID (sync_pg84_rds96) Totals: deletes=297 inserts=297 conflicts=0 (15337) [Thu Dec 5 08:51:25 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_accounts : 109 (15337) [Thu Dec 5 08:51:25 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_branches : 1 (15337) [Thu Dec 5 08:51:25 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_tellers : 10 (15337) [Thu Dec 5 08:51:25 2019] KID (sync_pg84_rds96) Totals: deletes=120 inserts=120 conflicts=0 (15337) [Thu Dec 5 08:51:26 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_accounts : 239 (15337) [Thu Dec 5 08:51:26 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_branches : 1 (15337) [Thu Dec 5 08:51:26 2019] KID (sync_pg84_rds96) Delta count for pgdb84.public.pgbench_tellers : 10 (15337) [Thu Dec 5 08:51:26 2019] KID (sync_pg84_rds96) Totals: deletes=250 inserts=250 conflicts=0 Conclusion This post demonstrated the complete solution to overcome the challenge of migrating legacy PostgreSQL databases older than 9.4 to Amazon RDS PostgreSQL or Aurora PostgreSQL by using the asynchronous trigger-based replication utility Bucardo. If you have comments or questions about this solution, please submit them in the comments section. About the Authors Rajeshkumar Sabankar is a Database Specialty Architect with Amazon Web Services. He works with internal Amazon customers to build secure, scalable, and resilient architectures in AWS Cloud and help customers perform migrations from on-premise databases to Amazon RDS and Aurora Databases. Samujjwal Roy is a Database Specialty Architect with the Professional Services team at Amazon Web Services. He has been with Amazon for 15+ years and has led migration projects for internal and external Amazon customers to move their on-premises database environment to AWS Cloud database solutions. https://probdm.com/site/MTk1Mzg

0 notes

mojoliciousblog · 8 years ago

Text

Let’s make browser testing fun again

Introduction

Tonight at the monthly Oslo.pm meetup, I gave a talk about how to test your web application in a real browser. This blog entry is a collection of the steps I went through while running live demos showcasing my module Test::Mojo::Role::Selenium.

My module uses Selenium::Remote::Driver which is a library that communicates with desktop browsers, such as Google Chrome, Firefox or even Internet Explorer. It comes bundled with test modules, but I wanted an interface that looks and feels like Mojolicious's test module Test::Mojo, since that module really makes testing fun.

Even if the module is a Test::Mojo role, it is not restricted to the Mojolicious web framework. The module can test any web site, as long as you have a web server running.

Why do you want to use this module?

Testing the HTTP messages for headers and body is great, but as soon as you make something other than an API or very simple web page, you should also test the user experience of the web app. Testing the JavaScript for dynamic web pages is the first that comes to mind, but responsive web pages also need testing, to see how elements are laid out on different screen sizes.

Test::Mojo::Role::Selenium allows you to write and run user experience tests in the browser of your selection. The syntax is very simple and it has sane defaults to avoid boilerplate in each test.

Prerequisites

To get started, you need to install the module and some executables that act as a glue between your test script and the browser of your selection.

# Install the test module $ cpanm Test::Mojo::Role::Selenium # Install Google Chrome, Firefox and PhantomJS drivers $ brew install chromedriver $ brew install geckodriver $ brew install phantomjs # Install the Selenium driver (requires jdk8) # brew install selenium-server-standalone

There are probably similar packages for your favorite operating system. The brew commands above are simply a cheat sheet for the presentation.

While preparing this article I wanted to get the demos running with Firefox, but I was not able to get the Selenium::Firefox module to work together with the geckodriver executable. Seems like the integration between firefox and geckodriver are under heavy development. Please let me know if I'm wrong. I did however manage to get Firefox running using the selenium-server. (I had to install Java though...)

You can change between the different backends using the MOJO_SELENIUM_DRIVER. environment variable. Note that Selenium::Chrome and Selenium::Firefox will start and stop the browser together with the test script, while Selenium::Remote::Driver (which uses selenium-server) require an external Selenium service to run.

Testing against a live web server

The first demo was to show that you can use the module to test any web site. The test mojolicious.t connects to mojolicious.org, checks for certain elements and fills in the search form, runs some JavaScript commands and then checks if the search result page was loaded.

Here are the commands I went through to run the demo:

$ mkdir -p test-selenium/t $ cd test-selenium $ vim t/mojolicious.t # copy/paste from t/mojolicious.t below # Test with Google chrome $ TEST_SELENIUM=http://mojolicious.org prove -vl t/mojolicious.t # Test with Firefox $ MOJO_SELENIUM_DRIVER=Selenium::Firefox \ TEST_SELENIUM=http://mojolicious.org \ prove -vl t/mojolicious.t # or... $ MOJO_SELENIUM_DRIVER=Selenium::Remote::Driver \ TEST_SELENIUM=http://mojolicious.org \ prove -vl t/mojolicious.t

The commands above should run the test script in various browser and result in a successful test run. Note that the environment variable TEST_SELENIUM need to be set, or the tests will be skipped. The reason for this is that I think in most cases the Selenium tests should not be run when installing a cpan module, nor being run on services such as Travis CI.

Testing against a local Mojolicious application

The next demo, internal.t, run tests agains a Mojolicious application. Using a Mojo app gives you some more features: In addition to test what is shown inside the browser, you can test headers and other "hidden" information that is exchanged over the HTTP protocol.

$ vim t/internal.t # copy/paste from t/internal.t below # Test with PhantomJS $ TEST_SELENIUM=1 prove -vl t/internal.t

Since the test script does not set MOJO_SELENIUM_DRIVER, it will use the default browser which is the headless browser PhantomJS. This browser is quite fast to start up, but might miss some features that is only available in Chrome, Firefox or Internet Explorer.

The headless version also takes screenshots which are saved to the operating system's temp directory. This can be changed by specifying screenshot_directory.

A more complex real life example

The last demo was to look at some tests for the Convos chat web application. The web app is a Mojolicious server that allows you to be persistently conected to IRC servers and communicate with other IRC users through your web browser. The frontend is powered by Vuejs, which is a reactive JavaScript library that can only be tested through the web browser.

The test suite feature many browser tests, (Look for the tests starting with selenium-) but the two tests that was demoed was selenium-url.t and selenium-register.t.

selenium-url.t

selenium-url.t simply tests the URL library url.js which is a URL parser and generator.

It does that by calling $t->driver->execute_script(...) which is a Selenium::Remote::Driver method for running JavaScript code inside the browser. The result from the method is then tested with normal Test::More functions.

selenium-register.t

selenium-register.t is a bit more complicated test that uses more features from Test::Mojo::Role::Selenium.

It uses wait_for to wait for elements that are injected dynamically to the document. wait_for() is a simple version of the more complex wait_until method that runs a function until the function returns a true value or a timeout runs out.

The end

I hope this introduction gave you an idea of what Test::Mojo::Role::Selenium can do, and makes testing fun again.

Resources

Links

Test::Mojo::Role::Selenium: API documentation.

Selenium::Remote::Driver: Holds information about what you can do with the driver.

Selenium::Remote::WebElement: Holds information about what you can do with an element.

Selenium::Remote::WDKeys: Check the source code for actual keys you can send to html elements.

t/mojolicious.t

use Mojo::Base -strict; use Test::Mojo::WithRoles "Selenium"; use Test::More; $ENV{MOJO_SELENIUM_DRIVER} ||= 'Selenium::Chrome'; my $t = Test::Mojo::WithRoles->new->setup_or_skip_all; $t->set_window_size([1024, 768]); $t->navigate_ok('/perldoc'); $t->current_url_is("http://mojolicious.org/perldoc"); $t->live_text_is('a[href="#GUIDES"]' => 'GUIDES'); $t->driver->execute_script( qq[document.querySelector("form")] .qq[.removeAttribute("target")]); $t->element_is_displayed("input[name=q]") ->send_keys_ok("input[name=q]", ["render", \"return"]); $t->wait_until(sub { $_->get_current_url =~ qr{q=render} }); $t->live_value_is("input[name=search]", "render"); done_testing;

t/internal.t

use Mojo::Base -strict; use Test::Mojo::WithRoles "Selenium"; use Test::More; use Mojolicious::Lite; get "/home" => "index"; my $t = Test::Mojo::WithRoles->new->setup_or_skip_all; $t->navigate_ok("/home") ->status_is(200) ->capture_screenshot ->header_is("Server" => "Mojolicious (Perl)") ->text_is("p" => "Hello!") ->live_text_is("p" => "Hello!") ->element_is_displayed("input") ->active_element_is("input[name=test]") ->send_keys_ok("input[name=test]", ["Yikes", \"enter"]); $t->current_url_like(qr{/home\?test=Yikes}) ->status_is(200) ->capture_screenshot ->live_element_exists("input[name=test][value=Yikes]"); done_testing; __DATA__ @@ index.html.ep <!DOCTYPE html> Test <p>Hello!</p> %= form_for "index", begin %= text_field 'test', autofocus => 1 %= submit_button % end

1 note · View note