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

Commit

Permalink
Issue #85 : changed the README files to reference to UBports (#86)
Browse files Browse the repository at this point in the history
* Clock App #85 : Updated the README file

* Clock App #85 : updated  README files

* Issue #85 : reverted to Ubuntu touch instead of UBports
  • Loading branch information
dark-eye authored and Flohack74 committed Jul 7, 2018
1 parent 77afff3 commit 4f61ee2
Show file tree
Hide file tree
Showing 5 changed files with 24 additions and 14 deletions.
16 changes: 13 additions & 3 deletions README
Expand Up @@ -11,9 +11,19 @@ Useful Links

Here are some useful links with regards to the Clock App development.

* Home Page - https://developer.ubuntu.com/en/community/core-apps/clock/
* Clock App Wiki - https://wiki.ubuntu.com/Touch/CoreApps/Clock
* Designs - https://drive.google.com/#folders/0B55Gs35e-jxxNzRzOHVxbmNDbFU
* Project page - https://github.com/ubports/clock-app
* Project translations - https://translate.ubports.com/projects/ubports/clock-app/
* Main UBports page - https://github.com/ubports
* Q&A Telegram group - https://t.me/ubports_qa_team
* UBports main page - https://ubports.com/


Old Ubuntu References
======================

* Home Page - https://developer.ubuntu.com/en/community/core-apps/clock/ (broken)
* Clock App Wiki - https://wiki.ubuntu.com/Touch/CoreApps/Clock (broken)
* Old Designs - https://drive.google.com/#folders/0B55Gs35e-jxxNzRzOHVxbmNDbFU
* Project page - https://launchpad.net/ubuntu-clock-app


4 changes: 2 additions & 2 deletions README.autopilot
Expand Up @@ -27,8 +27,8 @@ Running tests on the desktop

Using terminal:

* Branch the clock app code,
$ bzr branch lp:ubuntu-clock-app
* Get the clock app code,
$ git clone git@github.com:ubports/clock-app.git

* Build the clock app,
$ mkdir builddir && cd builddir
Expand Down
2 changes: 1 addition & 1 deletion README.mergeproposal → README.mergeproposal.old
Expand Up @@ -31,4 +31,4 @@ stable and up to date.

Jenkins
=======
In addition to manual reviews, merge proposals are subject to being run in jenkins to ensure the application builds and any unit tests are successful. For more information on jenkins and how it works, see the [Core Apps Jenkins Wiki](https://wiki.ubuntu.com/Touch/CoreApps/Jenkins)
In addition to manual reviews, merge proposals are subject to being run in jenkins to ensure the application builds and any unit tests are successful. For more information on jenkins and how it works, see the [Core Apps Jenkins Wiki](https://wiki.ubuntu.com/Touch/CoreApps/Jenkins)
4 changes: 2 additions & 2 deletions README.translations
@@ -1,7 +1,7 @@
Updating translations
=====================

Translations for the Clock app happen in [Launchpad Translations] and
Translations for the Clock app happen in [UBports Weblate] and
are automatically committed daily on the trunk branch in the po/ folder.

They are then built and installed as part of the package build, so that
Expand Down Expand Up @@ -38,5 +38,5 @@ language the app has got at least a translated message available for.

Translations for core apps follow the standard [gettext format].

[Launchpad Translations]: https://translations.launchpad.net/ubuntu-clock-app
[UBports Weblate]: https://translate.ubports.com/projects/ubports/clock-app/
[gettext format]: https://www.gnu.org/software/gettext/
12 changes: 6 additions & 6 deletions README.unittest
Expand Up @@ -9,17 +9,17 @@ If you are submitting your bugfix/patch to the clock app, please follow the
following steps below to check whether that all tests pass before proposing a
merge request.

* Branch the clock app code,
$ bzr branch lp:ubuntu-clock-app
* Get the clock app code,
$ git clone git@github.com:ubports/clock-app.git

* Build the clock app,
$ mkdir builddir && cd builddir
$ mkdir build && cd build
$ cmake .. && cmake --build . -- -j 3

Running all unit test at once
=============================

If you want to run all tests, then run the following command from the builddir,
If you want to run all tests, then run the following command from the build dir,

$ ctest --output-on-failure

Expand All @@ -34,8 +34,8 @@ If you want to run testcases individually, you can do so by navigating to the
unit tests folder by,

* Navigate to the tests/unit directory
$ cd tests/unit
$ cd <Project root>/tests/unit

* Run the test by providing their filenames
$ qmltestrunner -input tst_alarmLabel.qml
$ qmltestrunner -input tst_alarm.qml -import ../../builddir/backend
$ qmltestrunner -input tst_alarm.qml -import ../../build/backend

0 comments on commit 4f61ee2

Please sign in to comment.