You cannot use the existence of Test.sqlite to infer the script worked as if you simply issue your create table and roll it back you will still have a Test.sqlite file.
Anyone actually running the first example might get confused by the error being output twice if it fails - PrintError. e.g., if they run it from a dir they don't have write permission for.
Not all databases can rollback DDL changes - SQLite can but many others cannot so it might not be a good example.
rollback can also die.
In the second script execute can return true but not actually insert a row. Obviously it is not going to happen here as your SQL is inserting but it is a common mistake that beginners make to think because execute returns true the SQL actually did something e.g., an update which does not change anything usually returns 0 but true.