From 81c31f7245218f15f707cbb706e2ba37b614f161 Mon Sep 17 00:00:00 2001 From: Alexander Todorov Date: Tue, 5 Nov 2024 22:45:14 +0200 Subject: [PATCH] Generate Pelican site --- blog/archives/index.html | 4 + blog/authors/index.html | 2 +- blog/index.html | 105 +++--- blog/index2.html | 225 ++++------- blog/index3.html | 194 ++++++++-- blog/index4.html | 93 ++--- blog/index5.html | 311 +++------------- blog/index6.html | 289 +++++++++++++-- blog/index7.html | 154 ++------ blog/index8.html | 341 ++++++----------- blog/index9.html | 226 +++++++++++ .../index.html | 227 ++++++++++++ blog/kiwi-tcms-team/index.html | 187 +++------- blog/kiwi-tcms-team/index2.html | 205 +++++++--- blog/kiwi-tcms-team/index3.html | 350 +++--------------- blog/kiwi-tcms-team/index4.html | 315 ++++++++++++++-- blog/kiwi-tcms-team/index5.html | 62 ++-- blog/kiwi-tcms-team/index6.html | 188 ++-------- blog/kiwi-tcms-team/index7.html | 265 +++++++------ blog/kiwi-tcms-team/index8.html | 114 ++++++ feeds/all.atom.xml | 34 +- feeds/misc.atom.xml | 34 +- 22 files changed, 2152 insertions(+), 1773 deletions(-) create mode 100644 blog/kiwi-tcms-team/2024/11/05/important-changes-to-user-accounts-on-tenantkiwitcmsorg/index.html diff --git a/blog/archives/index.html b/blog/archives/index.html index fe6d9d94..504d476c 100644 --- a/blog/archives/index.html +++ b/blog/archives/index.html @@ -95,6 +95,10 @@

Archives

+

Tue 05 November 2024

+

+ Important changes to user accounts on *.tenant.kiwitcms.org +

Tue 29 October 2024

Testing and Continuous Delivery devroom, FOSDEM'25 diff --git a/blog/authors/index.html b/blog/authors/index.html index 7e47cf5f..03b13d25 100644 --- a/blog/authors/index.html +++ b/blog/authors/index.html @@ -99,7 +99,7 @@

Blog authors

Alexander Todorov (21)

-

Kiwi TCMS Team (144)

+

Kiwi TCMS Team (145)

Malcolm Shore (1)

diff --git a/blog/index.html b/blog/index.html index f8947469..d98b9765 100644 --- a/blog/index.html +++ b/blog/index.html @@ -95,6 +95,48 @@

Blog

+
+
+ +

Important changes to user accounts on *.tenant.kiwitcms.org

+ + +

Posted by + Kiwi TCMS Team + on Tue 05 November 2024 +

+
+ +
+

Hello testers, +starting today we are discontinuing the ability to register user +accounts on https://public.tenant.kiwitcms.org! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!

+

How does this affect users

+
    +
  • New account registrations via email+password are not possible anymore - use OAuth login
    • +
  • Existing users are able to login via OAuth and/or email+password - reset your password + if forgotten
    • +
  • New subscription purchases will create user accounts automatically - + reset your password before first login. + Note: existing subscribers already have accounts
    • +
  • Inviting new users to a Private Tenant, PLUGINS -> Tenant -> Invite users + will create user accounts automatically - reset your password before first login
    • +
+

Happy Testing!

+
+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+
-
-
- -

OffSec has chosen Kiwi TCMS

- - -

Posted by - Malcolm Shore - on Tue 18 July 2023 -

-
- -
-

OffSec is an American international company working -in information security, penetration testing and digital forensics. Operating -from around 2007, the company has created multiple open source projects, -advanced security courses, the ExploitDB vulnerability database, and the popular Kali Linux. -It has recently released the Kali Purple platform, a dedicated platform for -cyber defence analysts and a platform for security services.

-

Introduction to Assurance Testing -is a brand new training course covering the defensive testing techniques used -to establish a level of assurance that your server is secure. It is the first -course of OffSec’s OSDA cyber defence learning path. This course introduces the -context for security testing and explains how security testing aligns to the business.

-

Chapter 3: Creating and Using Security Test Documentation explains the documentation -used in security related testing and introduces Kiwi TCMS as the test management tool of choice! -"Kiwi TCMS as shown in OffSec's training materials"

-

The course is part of Offsec’s fundamentals package which is designed as baseline knowledge -and skills for all security professionals and in particular for those who wish to progress -to the OffSec Defence Analyst (OSDA) certification. The Assurance Testing course, -and the Kiwi TCMS tool which it uses, gives developers and security testers alike a good -understanding of the best practice approach to test case management and helps build their -skills in carrying out testing in a disciplined way. Using Kiwi TCMS provides the -opportunity to improve the processes and documentation around security testing, -and around the wider functional testing as well.

-

Kiwi TCMS bridges the gap between security requirements and software development by -enabling standardized test cases to be developed by the security team whilst -software developers and dedicated QA teams can use these same test cases to ensure that -security requirements are met. With preset test plans and test cases, -execution of security tests can proceed in the same way as for any other non-functional testing, -and any issues identified during testing can be fixed and tests can be executed again.

-

Learning how to use Kiwi TCMS as part of the Introduction to Assurance Testing course helps -both security teams and QA teams work together in a common environment to improve -the quality and security of their software. Using Kiwi TCMS enables security teams to -provide clear instructions to QA teams as to how to use specialist security testing tools. -For example, having clear test cases for running the PowerShell audit tool -for the Active Directory Certificate Server, PSPKIAudit, means that the test team can take advantage -of a powerful testing tool without needing the specialist knowledge that might otherwise be required -to use and interpret the results of such a tool.

-
-

If you like what we're doing and how Kiwi TCMS supports various communities -please help us!

-
diff --git a/blog/index2.html b/blog/index2.html index f2338f19..a86e99f4 100644 --- a/blog/index2.html +++ b/blog/index2.html @@ -95,6 +95,69 @@

Blog

+
+
+ +

OffSec has chosen Kiwi TCMS

+ + +

Posted by + Malcolm Shore + on Tue 18 July 2023 +

+
+ +
+

OffSec is an American international company working +in information security, penetration testing and digital forensics. Operating +from around 2007, the company has created multiple open source projects, +advanced security courses, the ExploitDB vulnerability database, and the popular Kali Linux. +It has recently released the Kali Purple platform, a dedicated platform for +cyber defence analysts and a platform for security services.

+

Introduction to Assurance Testing +is a brand new training course covering the defensive testing techniques used +to establish a level of assurance that your server is secure. It is the first +course of OffSec’s OSDA cyber defence learning path. This course introduces the +context for security testing and explains how security testing aligns to the business.

+

Chapter 3: Creating and Using Security Test Documentation explains the documentation +used in security related testing and introduces Kiwi TCMS as the test management tool of choice! +"Kiwi TCMS as shown in OffSec's training materials"

+

The course is part of Offsec’s fundamentals package which is designed as baseline knowledge +and skills for all security professionals and in particular for those who wish to progress +to the OffSec Defence Analyst (OSDA) certification. The Assurance Testing course, +and the Kiwi TCMS tool which it uses, gives developers and security testers alike a good +understanding of the best practice approach to test case management and helps build their +skills in carrying out testing in a disciplined way. Using Kiwi TCMS provides the +opportunity to improve the processes and documentation around security testing, +and around the wider functional testing as well.

+

Kiwi TCMS bridges the gap between security requirements and software development by +enabling standardized test cases to be developed by the security team whilst +software developers and dedicated QA teams can use these same test cases to ensure that +security requirements are met. With preset test plans and test cases, +execution of security tests can proceed in the same way as for any other non-functional testing, +and any issues identified during testing can be fixed and tests can be executed again.

+

Learning how to use Kiwi TCMS as part of the Introduction to Assurance Testing course helps +both security teams and QA teams work together in a common environment to improve +the quality and security of their software. Using Kiwi TCMS enables security teams to +provide clear instructions to QA teams as to how to use specialist security testing tools. +For example, having clear test cases for running the PowerShell audit tool +for the Active Directory Certificate Server, PSPKIAudit, means that the test team can take advantage +of a powerful testing tool without needing the specialist knowledge that might otherwise be required +to use and interpret the results of such a tool.

+
+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+
-
-
- -

Kiwi TCMS 11.2

- - -

Posted by - Kiwi TCMS Team - on Wed 09 March 2022 -

-
- -
-

We're happy to announce Kiwi TCMS version 11.2.

-

IMPORTANT: -This is a small release which contains several improvements, new API methods, -internal refactoring and new translations! This is the first release to ship -aarch64 container images!

-

You can explore everything at -https://public.tenant.kiwitcms.org!

-
-

Supported upgrade paths:

-
-5.3   (or older) -> 5.3.1
-5.3.1 (or newer) -> 6.0.1
-6.0.1            -> 6.1
-6.1              -> 6.1.1
-6.1.1            -> 6.2 (or newer)
-
-
-

---

-
-

Upstream container images (x86_64):

-
-kiwitcms/kiwi   latest  bcc4c658440a    622MB
-
-
-

IMPORTANT: version tagged and multi-arch -container images are available only to -subscribers!

-
-

Changes since Kiwi TCMS 11.1

-
-

Improvements

-
    -
  • Update django from 4.0.2 to 4.0.3
    • -
  • Update django-grappelli from 3.0.2 to 3.0.3
    • -
  • Update django-simple-captcha from 0.5.14 to 0.5.17
    • -
  • Update python-bugzilla from 3.1.0 to 3.2.0
    • -
  • Update python-gitlab from 3.1.1 to 3.2.0
    • -
  • Update node_modules/prismjs from 1.26.0 to 1.27.0
    • -
  • Add new command to perform a collection of post-upgrade tasks. -Kiwi TCMS admins are advised to replace -manage.py migrate with manage.py upgrade (Ivajlo Karabojkov)
    • -
-
-
-

API

-
    -
  • New API method Category.create(). Fixes -Issue #2705 (Erik Heeren)
    • -
  • New API method Classification.create(). Fixes -Issue #2705 (Erik Heeren)
    • -
-
-
-

Refactoring and testing

-
    -
  • Add docker build & push automation
    • -
  • Fix Bandit exclusion rule
    • -
  • Test and build on aarch64
    • -
  • Apply auto fixes fro pre-commit.ci
    • -
  • Apply auto fixes from Deepsource
    • -
  • Update versions of several GitHub Actions
    • -
  • Use the appropriate path to package.json for Dependabot
    • -
  • Remove old Telemetry link in menu to avoid confusion
    • -
-
- -
-
-

Kiwi TCMS Enterprise v11.2-mt

-
    -

  • Based on Kiwi TCMS v11.2

    -
    • -

  • Update django-ses from 2.4.0 to 2.6.0

    -
    • -

  • Update python3-saml from 1.13.0 to 1.14.0

    -
    • -

  • Revert "Use django.contrib.staticfiles.storage from Django==3.2.12". -Instead use the implementation from latest Django version. Closes -Issue #140

    -
    • -

  • Start building kiwitcms/enterprise on aarch64

    -
    • -

  • Add changelog check & docker release automation

    -
    • -

  • Add test for PSA login URLs on login page. References -Issue #83

    -
    • -

  • Add SAML & Azure AD logo images

    -
    • -

  • Update GitHub Actions

    -
    • -

  • Hard-code testing with Keycloak 16.1.1 to workaround significant differences -with Keycloak v17 container

    -
    -

    Private images:

    -
    -quay.io/kiwitcms/enterprise         11.2-mt (aarch64)   fe5e869e36f6    09 Mar 2022    890MB
-quay.io/kiwitcms/enterprise         11.2-mt (x86_64)    134320d5fb7c    09 Mar 2022    841MB
-quay.io/kiwitcms/version            11.2 (aarch64)      3b782830d19d    09 Mar 2022    665MB
-quay.io/kiwitcms/version            11.2 (x86_64)       bcc4c658440a    09 Mar 2022    620MB
-
    -
    -
    • -
-

IMPORTANT: version tagged, multi-arch and Enterprise -container images are available only to -subscribers!

-
-
-

How to upgrade

-

Backup first! -Then execute the commands:

-
-cd path/containing/docker-compose/
-docker-compose down
-docker-compose pull
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py upgrade
-
-

Refer to -our documentation -for more details!

-

Happy testing!

-

---

-

If you like what we're doing and how Kiwi TCMS supports various communities -please help us!

-
diff --git a/blog/index3.html b/blog/index3.html index 9bb0f831..d61bea5d 100644 --- a/blog/index3.html +++ b/blog/index3.html @@ -95,6 +95,168 @@

Blog

+
+
+ +

Kiwi TCMS 11.2

+ + +

Posted by + Kiwi TCMS Team + on Wed 09 March 2022 +

+
+ +
+

We're happy to announce Kiwi TCMS version 11.2.

+

IMPORTANT: +This is a small release which contains several improvements, new API methods, +internal refactoring and new translations! This is the first release to ship +aarch64 container images!

+

You can explore everything at +https://public.tenant.kiwitcms.org!

+
+

Supported upgrade paths:

+
+5.3   (or older) -> 5.3.1
+5.3.1 (or newer) -> 6.0.1
+6.0.1            -> 6.1
+6.1              -> 6.1.1
+6.1.1            -> 6.2 (or newer)
+
+
+

---

+
+

Upstream container images (x86_64):

+
+kiwitcms/kiwi   latest  bcc4c658440a    622MB
+
+
+

IMPORTANT: version tagged and multi-arch +container images are available only to +subscribers!

+
+

Changes since Kiwi TCMS 11.1

+
+

Improvements

+
    +
  • Update django from 4.0.2 to 4.0.3
    • +
  • Update django-grappelli from 3.0.2 to 3.0.3
    • +
  • Update django-simple-captcha from 0.5.14 to 0.5.17
    • +
  • Update python-bugzilla from 3.1.0 to 3.2.0
    • +
  • Update python-gitlab from 3.1.1 to 3.2.0
    • +
  • Update node_modules/prismjs from 1.26.0 to 1.27.0
    • +
  • Add new command to perform a collection of post-upgrade tasks. +Kiwi TCMS admins are advised to replace +manage.py migrate with manage.py upgrade (Ivajlo Karabojkov)
    • +
+
+
+

API

+
    +
  • New API method Category.create(). Fixes +Issue #2705 (Erik Heeren)
    • +
  • New API method Classification.create(). Fixes +Issue #2705 (Erik Heeren)
    • +
+
+
+

Refactoring and testing

+
    +
  • Add docker build & push automation
    • +
  • Fix Bandit exclusion rule
    • +
  • Test and build on aarch64
    • +
  • Apply auto fixes fro pre-commit.ci
    • +
  • Apply auto fixes from Deepsource
    • +
  • Update versions of several GitHub Actions
    • +
  • Use the appropriate path to package.json for Dependabot
    • +
  • Remove old Telemetry link in menu to avoid confusion
    • +
+
+ +
+
+

Kiwi TCMS Enterprise v11.2-mt

+
    +

  • Based on Kiwi TCMS v11.2

    +
    • +

  • Update django-ses from 2.4.0 to 2.6.0

    +
    • +

  • Update python3-saml from 1.13.0 to 1.14.0

    +
    • +

  • Revert "Use django.contrib.staticfiles.storage from Django==3.2.12". +Instead use the implementation from latest Django version. Closes +Issue #140

    +
    • +

  • Start building kiwitcms/enterprise on aarch64

    +
    • +

  • Add changelog check & docker release automation

    +
    • +

  • Add test for PSA login URLs on login page. References +Issue #83

    +
    • +

  • Add SAML & Azure AD logo images

    +
    • +

  • Update GitHub Actions

    +
    • +

  • Hard-code testing with Keycloak 16.1.1 to workaround significant differences +with Keycloak v17 container

    +
    +

    Private images:

    +
    +quay.io/kiwitcms/enterprise         11.2-mt (aarch64)   fe5e869e36f6    09 Mar 2022    890MB
+quay.io/kiwitcms/enterprise         11.2-mt (x86_64)    134320d5fb7c    09 Mar 2022    841MB
+quay.io/kiwitcms/version            11.2 (aarch64)      3b782830d19d    09 Mar 2022    665MB
+quay.io/kiwitcms/version            11.2 (x86_64)       bcc4c658440a    09 Mar 2022    620MB
+
    +
    +
    • +
+

IMPORTANT: version tagged, multi-arch and Enterprise +container images are available only to +subscribers!

+
+
+

How to upgrade

+

Backup first! +Then execute the commands:

+
+cd path/containing/docker-compose/
+docker-compose down
+docker-compose pull
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py upgrade
+
+

Refer to +our documentation +for more details!

+

Happy testing!

+

---

+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+ +
+
-
-
- -

Thank you for downloading Kiwi TCMS 500000 times

- - -

Posted by - Kiwi TCMS Team - on Tue 15 June 2021 -

-
- -
-

"500K banner"

-

We are happy to announce that Kiwi TCMS has been downloaded more than -500000 times via Docker Hub! -You can check the real-time stats -here.

-

Thank you very much and Happy Testing!

-
-

If you like what we're doing and how Kiwi TCMS supports various communities -please help us!

- -
-
Newer Posts diff --git a/blog/index4.html b/blog/index4.html index 3e0ab44f..bdc88b52 100644 --- a/blog/index4.html +++ b/blog/index4.html @@ -95,6 +95,38 @@

Blog

+
+
+ +

Thank you for downloading Kiwi TCMS 500000 times

+ + +

Posted by + Kiwi TCMS Team + on Tue 15 June 2021 +

+
+ +
+

"500K banner"

+

We are happy to announce that Kiwi TCMS has been downloaded more than +500000 times via Docker Hub! +You can check the real-time stats +here.

+

Thank you very much and Happy Testing!

+
+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+
-
-
- -

Kiwi TCMS container images now available via Red Hat Quay.io

- - -

Posted by - Kiwi TCMS Team - on Tue 18 August 2020 -

-
- -
-

Hello testers, we have very important news around how container images -for Kiwi TCMS will be distributed! Recently Docker has announced -several changes in their storage plans which makes it less viable for -our team to continue using their services in full!

-

Information about official upstream container images

-

The official upstream Kiwi TCMS container image will continue to be -publicly available via Docker Hub -as before. In addition all existing and new images will be available via -Quay.io. -These images are available as

- -

Content is exactly the same between the two registries and you may use -the one which you like best!

-

Warning: after November 1st 2020 older versions will not be available from -Docker Hub, only from Quay.io! The reason is that Docker is enforcing a -6 month image retention limit -for free plans!

-

Information about private containers for subscribers

-

Subscribers enjoy the benefit of having read-only access to tagged versions of the -upstream Kiwi TCMS container images as well as access to tagged versions of -Kiwi TCMS Enterprise container images! Previously these containers were distributed -via Docker Hub and are now available via Quay.io:

-
    -
  • mrsenko/kiwitcms -> quay.io/kiwitcms/version (version tagged upstream images)
    • -
  • mrsenko/kiwitcms-enterprise -> quay.io/kiwitcms/enterprise (enterprise images)
    • -
-

Important: existing subscribers have been notified and granted access -to the new repositories on Quay.io. We advise you to update your -docker-compose.yml files and start using the new images at your earliest convenience!

-

Warning: existing subscribers will continue having access to private -repositories on Docker Hub until December 31st 2020! Private repositories on -Docker Hub will become unavailable after January 31st, 2021 when Docker's new -storage plans will be forced into effect!

-

Why did we chose Quay.io

-

There are multiple container registry services available! We think Quay.io -delivers the best price/quality ratio for our own use-case. In particular -we like the billing model around number of private repositories instead the -one around the number of users in your organization. That's very similar -to how we provide access to Kiwi TCMS via our own subscriptions!

-

Also it just looks cool if you employ your imagination, especially -for non-native English speakers: quay -> qu-ai -> QA!

-


-Thanks for reading and happy testing!

-
-
Newer Posts diff --git a/blog/index5.html b/blog/index5.html index 7efe3d3a..16f174f8 100644 --- a/blog/index5.html +++ b/blog/index5.html @@ -95,6 +95,67 @@

Blog

+
+
+ +

Kiwi TCMS container images now available via Red Hat Quay.io

+ + +

Posted by + Kiwi TCMS Team + on Tue 18 August 2020 +

+
+ +
+

Hello testers, we have very important news around how container images +for Kiwi TCMS will be distributed! Recently Docker has announced +several changes in their storage plans which makes it less viable for +our team to continue using their services in full!

+

Information about official upstream container images

+

The official upstream Kiwi TCMS container image will continue to be +publicly available via Docker Hub +as before. In addition all existing and new images will be available via +Quay.io. +These images are available as

+ +

Content is exactly the same between the two registries and you may use +the one which you like best!

+

Warning: after November 1st 2020 older versions will not be available from +Docker Hub, only from Quay.io! The reason is that Docker is enforcing a +6 month image retention limit +for free plans!

+

Information about private containers for subscribers

+

Subscribers enjoy the benefit of having read-only access to tagged versions of the +upstream Kiwi TCMS container images as well as access to tagged versions of +Kiwi TCMS Enterprise container images! Previously these containers were distributed +via Docker Hub and are now available via Quay.io:

+
    +
  • mrsenko/kiwitcms -> quay.io/kiwitcms/version (version tagged upstream images)
    • +
  • mrsenko/kiwitcms-enterprise -> quay.io/kiwitcms/enterprise (enterprise images)
    • +
+

Important: existing subscribers have been notified and granted access +to the new repositories on Quay.io. We advise you to update your +docker-compose.yml files and start using the new images at your earliest convenience!

+

Warning: existing subscribers will continue having access to private +repositories on Docker Hub until December 31st 2020! Private repositories on +Docker Hub will become unavailable after January 31st, 2021 when Docker's new +storage plans will be forced into effect!

+

Why did we chose Quay.io

+

There are multiple container registry services available! We think Quay.io +delivers the best price/quality ratio for our own use-case. In particular +we like the billing model around number of private repositories instead the +one around the number of users in your organization. That's very similar +to how we provide access to Kiwi TCMS via our own subscriptions!

+

Also it just looks cool if you employ your imagination, especially +for non-native English speakers: quay -> qu-ai -> QA!

+


+Thanks for reading and happy testing!

+
+
-
-
- -

Kiwi TCMS 8.0

- - -

Posted by - Kiwi TCMS Team - on Wed 12 February 2020 -

-
- -
-

We're happy to announce Kiwi TCMS version 8.0!

-

IMPORTANT: this is a major release which includes important database and -API changes, several improvements and bug fixes. Multiple API methods are now -incompatible with older releases and extra caution needs to be applied when -upgrading via docker-compose.yml because newer MariaDB versions are -breaking direct upgrades from existing installations!

-

You can explore everything at -https://public.tenant.kiwitcms.org!

-

Supported upgrade paths:

-
-5.3   (or older) -> 5.3.1
-5.3.1 (or newer) -> 6.0.1
-6.0.1            -> 6.1
-6.1              -> 6.1.1
-6.1.1            -> 6.2 (or newer)
-
-

Docker images:

-
-kiwitcms/kiwi       latest  71a55e353da2    557 MB
-kiwitcms/kiwi       6.2     7870085ad415    957 MB
-kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955 MB
-kiwitcms/kiwi       6.1     b559123d25b0    970 MB
-kiwitcms/kiwi       6.0.1   87b24d94197d    970 MB
-kiwitcms/kiwi       5.3.1   a420465852be    976 MB
-
-
-

Changes since Kiwi TCMS 7.3

-
-

Improvements

-
    -
  • Update Django from 3.0.2 to 3.0.3
    • -
  • Update django-grappelli from 2.13.3 to 2.14.1
    • -
  • Update markdown from 3.1.1 to 3.2
    • -
  • Update python-gitlab from 1.15.0 to 2.0.1
    • -
  • Update pygithub from 1.45 to 1.46
    • -
  • Allow customization of test execution statuses via admin. -For more information see -https://kiwitcms.readthedocs.io/en/latest/admin.html#test-execution-statuses. -Fixes Issue #236
    • -
  • Add passing rate chart to Execution trends telemetry
    • -
  • Documentation updates (@Prome88)
    • -
-
-
-

Database

-

This release adds several migrations which alter the underlying database schema -by renaming multiple columns.

-

WARNINGS:

-
    -

  • SQLite has very poor capabilities for altering schema and it will break -when run with existing database! If you had deployed Kiwi TCMS with -SQLite for production purposes you will not be able to upgrade! We recommend -switching to Postgres first and then upgrading!

    -
    • -

  • docker-compose.yml has been updated from MariaDB 5.5 to MariaDB 10.3. -The 10.x MariaDB containers change their datadir configuration from -/var/lib/mysql to /var/lib/mysql/data! We recommend first upgrading -your MariaDB version, using Kiwi TCMS 7.3 and afterwards upgrading to -Kiwi TCMS 8.0:

    -
      -

    1. Backup existing database with:

      -
      -docker exec -it kiwi_db mysqldump -u kiwi -pYourPass kiwi > backup.sql
-
      -
      2. -

    2. docker-compose down

      -
      3. -

    3. docker volume rm kiwi_db_data - will remove existing data volume -b/c of incompatibilities between different MariaDB versions

      -
      4. -

    4. docker-compose up - will recreate data volume with missing data. e.g. -manage.py showmigrations will report that 0 migrations have been applied.

      -
      5. -

    5. Restore the data from backup:

      -
      -cat backup.sql | docker exec -u 0 -i kiwi_db /opt/rh/rh-mariadb103/root/usr/bin/mysql kiwi
-
      -

      note: This connects to the database as the root user

      -
      6. -

    6. Proceed to upgrade your Kiwi TCMS container !

      -
      7. -
    -
    • -
-

CHANGES:

-
    -
  • Remove model fields of type AutoField. They are a legacy construct -and shouldn't be specified in the source code! Django knows how to add them -dynamically. These are:
      -
    • Tag.id
      • -
    • TestCaseStatus.id
      • -
    • Category.id
      • -
    • PlanType.id
      • -
    • TestExecutionStatus.id
      • -
    -
    • -
  • Remove db_column attribute from model fields
    • -
  • Rename several primary key fields to id:
      -
    • Build.build_id -> Build.id
      • -
    • TestRun.run_id -> TestRun.id
      • -
    • TestPlan.plan_id -> TestPlan.id
      • -
    • TestCase.case_id -> TestCase.id
      • -
    • TestExecution.case_run_id -> TestExecution.id
      • -
    -
    • -
-
-
-

API

-

WARNING:

-

The database schema changes mentioned above affect multiple API methods -in a backwards incompatible way! -There is possibility that your API scripts will also be affected. You will -have to adjust those to use the new field names where necessary!

-

CHANGES:

-
    -
  • Methods Build.create(), Build.filter() and Build.update() will -return id instead of build_id field
    • -
  • Method TestRun.get_cases() will return execution_id instead of -case_run_id field and id instead of case_id field
    • -
  • Methods TestRun.add_case(), TestExecution.create(), -TestExecution.filter() and TestExecution.update() will return -id instead of case_run_id field
    • -
  • Methods TestRun.create(), TestRun.filter(), TestRun.update() will -return id instead of run_id field
    • -
  • Methods TestPlan.create(), TestPlan.filter() and -TestPlan.update() will return id instead of plan_id field
    • -
  • Methods TestCase.add_component(), TestCase.create(), -TestCase.filter() and TestCase.update() will return id instead -of case_id field
    • -
-

NOTES:

-

Kiwi TCMS automation framework plugins have been updated to work with the -newest API. At the time of Kiwi TCMS v8.0 release their versions are:

-
    -
  • kiwitcms-tap-plugin v8.0.1
    • -
  • kiwitcms-junit.xml-plugin v8.0.1
    • -
  • kiwitcms-junit-plugin v8.0
    • -
-
-
-

Bug fixes

-
    -
  • Allow displaying lists with more then 9 items when reviewing test cases. Fixes -Issue #339 (Mfon Eti-mfon)
    • -
  • Make tcms.tests.storage.RaiseWhenFileNotFound` capable of finding -finding static files on Windows which enables development mode for folks -not using Linux environment. See -SO #55297178 (Mfon Eti-mfon)
    • -
  • Allow changing test execution status without adding comment. Fixes -Issue #1261
    • -
  • Properly refresh test run progress bar when changing statuses. Fixes -Issue #1326
    • -
  • Fix a bug where updating test cases from the UI was causing text and various -other fields to be reset. Fixes -Issue #1318
    • -
-
-
-

Refactoring

-
    -
  • Extract attachments widget to new template. Fixes -Issue #1124 -(Rosen Sasov)
    • -
  • Rename RPC related classes. Fixes -Issue #682 -(Rosen Sasov)
    • -
  • Add new test (Mariyan Garvanski)
    • -
  • Start using GitHub actions, first for running flake8
    • -
  • Remove unused TestCase.get_previous_and_next()
    • -
  • Remove unused TestCaseStatus.string_to_instance()
    • -
  • Remove unused TestCase.create()
    • -
  • Remove unused json_success_refresh_page()
    • -
  • Remove unused fields from SearchPlanForm
    • -
  • Use JSON-RPC in previewPlan()
    • -
  • Remove toggleTestCaseContents(), duplicate of toggleTestExecutionPane()
    • -
  • Refactor a few more views to class-based
    • -
-
-
-

Translations

- -
-
-
-

GitHub Marketplace listing deprecation

-

As we've stated previously Kiwi TCMS has migrated to a new GitHub backend and -OAuth tokens for the previous backend have been revoked and the -existing listing on GitHub Marketplace is deprecated. It is a non-functioning -app at the moment!

-

It is not possible for us to cancel Marketplace subscriptions programatically, -that is GitHub does not provide such API. Active subscribers please follow these -3 steps to help us clean up stale information:

-
    -
  • Go to https://github.com/marketplace/kiwi-tcms
    • -
  • From "Edit your plan" button at the top select your GitHub account
    • -
  • Then click "Cancel this plan" link which is at the left-hand side -at the bottom of the description box!
    • -
-
-
-

How to upgrade

-

Backup first! -If you are using Kiwi TCMS as a Docker container then:

-
-cd path/containing/docker-compose/
-docker-compose down
-docker pull kiwitcms/kiwi
-docker pull centos/mariadb-103-centos7
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-
-

WHERE: docker-compose.yml has been updated from your private git repository! -The file provided in our GitHub repository is an example. Not for production use!

-

WARNING: kiwitcms/kiwi:latest and docker-compose.yml will -always point to the latest available version! If you have to upgrade in steps, -e.g. between several intermediate releases, you have to modify the above workflow:

-
-# starting from an older Kiwi TCMS version
-docker-compose down
-docker pull kiwitcms/kiwi:<next_upgrade_version>
-edit docker-compose.yml to use kiwitcms/kiwi:<next_upgrade_version>
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-# repeat until you have reached latest
-
-

Happy testing!

-
- -
-
Newer Posts diff --git a/blog/index6.html b/blog/index6.html index ca21e146..79c94bff 100644 --- a/blog/index6.html +++ b/blog/index6.html @@ -95,6 +95,256 @@

Blog

+
+
+ +

Kiwi TCMS 8.0

+ + +

Posted by + Kiwi TCMS Team + on Wed 12 February 2020 +

+
+ +
+

We're happy to announce Kiwi TCMS version 8.0!

+

IMPORTANT: this is a major release which includes important database and +API changes, several improvements and bug fixes. Multiple API methods are now +incompatible with older releases and extra caution needs to be applied when +upgrading via docker-compose.yml because newer MariaDB versions are +breaking direct upgrades from existing installations!

+

You can explore everything at +https://public.tenant.kiwitcms.org!

+

Supported upgrade paths:

+
+5.3   (or older) -> 5.3.1
+5.3.1 (or newer) -> 6.0.1
+6.0.1            -> 6.1
+6.1              -> 6.1.1
+6.1.1            -> 6.2 (or newer)
+
+

Docker images:

+
+kiwitcms/kiwi       latest  71a55e353da2    557 MB
+kiwitcms/kiwi       6.2     7870085ad415    957 MB
+kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955 MB
+kiwitcms/kiwi       6.1     b559123d25b0    970 MB
+kiwitcms/kiwi       6.0.1   87b24d94197d    970 MB
+kiwitcms/kiwi       5.3.1   a420465852be    976 MB
+
+
+

Changes since Kiwi TCMS 7.3

+
+

Improvements

+
    +
  • Update Django from 3.0.2 to 3.0.3
    • +
  • Update django-grappelli from 2.13.3 to 2.14.1
    • +
  • Update markdown from 3.1.1 to 3.2
    • +
  • Update python-gitlab from 1.15.0 to 2.0.1
    • +
  • Update pygithub from 1.45 to 1.46
    • +
  • Allow customization of test execution statuses via admin. +For more information see +https://kiwitcms.readthedocs.io/en/latest/admin.html#test-execution-statuses. +Fixes Issue #236
    • +
  • Add passing rate chart to Execution trends telemetry
    • +
  • Documentation updates (@Prome88)
    • +
+
+
+

Database

+

This release adds several migrations which alter the underlying database schema +by renaming multiple columns.

+

WARNINGS:

+
    +

  • SQLite has very poor capabilities for altering schema and it will break +when run with existing database! If you had deployed Kiwi TCMS with +SQLite for production purposes you will not be able to upgrade! We recommend +switching to Postgres first and then upgrading!

    +
    • +

  • docker-compose.yml has been updated from MariaDB 5.5 to MariaDB 10.3. +The 10.x MariaDB containers change their datadir configuration from +/var/lib/mysql to /var/lib/mysql/data! We recommend first upgrading +your MariaDB version, using Kiwi TCMS 7.3 and afterwards upgrading to +Kiwi TCMS 8.0:

    +
      +

    1. Backup existing database with:

      +
      +docker exec -it kiwi_db mysqldump -u kiwi -pYourPass kiwi > backup.sql
+
      +
      2. +

    2. docker-compose down

      +
      3. +

    3. docker volume rm kiwi_db_data - will remove existing data volume +b/c of incompatibilities between different MariaDB versions

      +
      4. +

    4. docker-compose up - will recreate data volume with missing data. e.g. +manage.py showmigrations will report that 0 migrations have been applied.

      +
      5. +

    5. Restore the data from backup:

      +
      +cat backup.sql | docker exec -u 0 -i kiwi_db /opt/rh/rh-mariadb103/root/usr/bin/mysql kiwi
+
      +

      note: This connects to the database as the root user

      +
      6. +

    6. Proceed to upgrade your Kiwi TCMS container !

      +
      7. +
    +
    • +
+

CHANGES:

+
    +
  • Remove model fields of type AutoField. They are a legacy construct +and shouldn't be specified in the source code! Django knows how to add them +dynamically. These are:
      +
    • Tag.id
      • +
    • TestCaseStatus.id
      • +
    • Category.id
      • +
    • PlanType.id
      • +
    • TestExecutionStatus.id
      • +
    +
    • +
  • Remove db_column attribute from model fields
    • +
  • Rename several primary key fields to id:
      +
    • Build.build_id -> Build.id
      • +
    • TestRun.run_id -> TestRun.id
      • +
    • TestPlan.plan_id -> TestPlan.id
      • +
    • TestCase.case_id -> TestCase.id
      • +
    • TestExecution.case_run_id -> TestExecution.id
      • +
    +
    • +
+
+
+

API

+

WARNING:

+

The database schema changes mentioned above affect multiple API methods +in a backwards incompatible way! +There is possibility that your API scripts will also be affected. You will +have to adjust those to use the new field names where necessary!

+

CHANGES:

+
    +
  • Methods Build.create(), Build.filter() and Build.update() will +return id instead of build_id field
    • +
  • Method TestRun.get_cases() will return execution_id instead of +case_run_id field and id instead of case_id field
    • +
  • Methods TestRun.add_case(), TestExecution.create(), +TestExecution.filter() and TestExecution.update() will return +id instead of case_run_id field
    • +
  • Methods TestRun.create(), TestRun.filter(), TestRun.update() will +return id instead of run_id field
    • +
  • Methods TestPlan.create(), TestPlan.filter() and +TestPlan.update() will return id instead of plan_id field
    • +
  • Methods TestCase.add_component(), TestCase.create(), +TestCase.filter() and TestCase.update() will return id instead +of case_id field
    • +
+

NOTES:

+

Kiwi TCMS automation framework plugins have been updated to work with the +newest API. At the time of Kiwi TCMS v8.0 release their versions are:

+
    +
  • kiwitcms-tap-plugin v8.0.1
    • +
  • kiwitcms-junit.xml-plugin v8.0.1
    • +
  • kiwitcms-junit-plugin v8.0
    • +
+
+
+

Bug fixes

+
    +
  • Allow displaying lists with more then 9 items when reviewing test cases. Fixes +Issue #339 (Mfon Eti-mfon)
    • +
  • Make tcms.tests.storage.RaiseWhenFileNotFound` capable of finding +finding static files on Windows which enables development mode for folks +not using Linux environment. See +SO #55297178 (Mfon Eti-mfon)
    • +
  • Allow changing test execution status without adding comment. Fixes +Issue #1261
    • +
  • Properly refresh test run progress bar when changing statuses. Fixes +Issue #1326
    • +
  • Fix a bug where updating test cases from the UI was causing text and various +other fields to be reset. Fixes +Issue #1318
    • +
+
+
+

Refactoring

+
    +
  • Extract attachments widget to new template. Fixes +Issue #1124 +(Rosen Sasov)
    • +
  • Rename RPC related classes. Fixes +Issue #682 +(Rosen Sasov)
    • +
  • Add new test (Mariyan Garvanski)
    • +
  • Start using GitHub actions, first for running flake8
    • +
  • Remove unused TestCase.get_previous_and_next()
    • +
  • Remove unused TestCaseStatus.string_to_instance()
    • +
  • Remove unused TestCase.create()
    • +
  • Remove unused json_success_refresh_page()
    • +
  • Remove unused fields from SearchPlanForm
    • +
  • Use JSON-RPC in previewPlan()
    • +
  • Remove toggleTestCaseContents(), duplicate of toggleTestExecutionPane()
    • +
  • Refactor a few more views to class-based
    • +
+
+
+

Translations

+ +
+
+
+

GitHub Marketplace listing deprecation

+

As we've stated previously Kiwi TCMS has migrated to a new GitHub backend and +OAuth tokens for the previous backend have been revoked and the +existing listing on GitHub Marketplace is deprecated. It is a non-functioning +app at the moment!

+

It is not possible for us to cancel Marketplace subscriptions programatically, +that is GitHub does not provide such API. Active subscribers please follow these +3 steps to help us clean up stale information:

+
    +
  • Go to https://github.com/marketplace/kiwi-tcms
    • +
  • From "Edit your plan" button at the top select your GitHub account
    • +
  • Then click "Cancel this plan" link which is at the left-hand side +at the bottom of the description box!
    • +
+
+
+

How to upgrade

+

Backup first! +If you are using Kiwi TCMS as a Docker container then:

+
+cd path/containing/docker-compose/
+docker-compose down
+docker pull kiwitcms/kiwi
+docker pull centos/mariadb-103-centos7
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+
+

WHERE: docker-compose.yml has been updated from your private git repository! +The file provided in our GitHub repository is an example. Not for production use!

+

WARNING: kiwitcms/kiwi:latest and docker-compose.yml will +always point to the latest available version! If you have to upgrade in steps, +e.g. between several intermediate releases, you have to modify the above workflow:

+
+# starting from an older Kiwi TCMS version
+docker-compose down
+docker pull kiwitcms/kiwi:<next_upgrade_version>
+edit docker-compose.yml to use kiwitcms/kiwi:<next_upgrade_version>
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+# repeat until you have reached latest
+
+

Happy testing!

+
+ +
+
-
-
- -

Kiwi TCMS needs your help winning OpenAwards 2019

- - -

Posted by - Kiwi TCMS Team - on Mon 27 May 2019 -

-
- -
-

Vote for Kiwi TCMS at OpenAwards 2019

-

Thanks to you, our community supporters, Anton Sankov and Alex Todorov -took the lead at OpenExpo 2019 CfP votes. -We need your help one more time. Our team has submitted participation in -'Best Tech Community' and 'Best Success Story' categories.

-

Unfortunately our submission into 'Best Success Story' has been pulled down! -We used that category to share the story from a dead open source project into -a thriving open source community with lots of users and contributors and to -highlight some of our milestones. Here's the short version:

-
    -
  • lots of technical updates and refactoring, latest everything, modern UI
    • -
  • the only open source test case management system on GitHub Marketplace
    • -
  • nearly 60000 downloads on Docker Hub
    • -
  • growing and active core team
    • -
  • active OSS contributors
    • -
-

Please help us gain more recognition:

- -

Thanks you & happy testing!

-
-
Newer Posts diff --git a/blog/index7.html b/blog/index7.html index 5025795d..3eb5fa8d 100644 --- a/blog/index7.html +++ b/blog/index7.html @@ -95,6 +95,45 @@

Blog

+
+
+ +

Kiwi TCMS needs your help winning OpenAwards 2019

+ + +

Posted by + Kiwi TCMS Team + on Mon 27 May 2019 +

+
+ +
+

Vote for Kiwi TCMS at OpenAwards 2019

+

Thanks to you, our community supporters, Anton Sankov and Alex Todorov +took the lead at OpenExpo 2019 CfP votes. +We need your help one more time. Our team has submitted participation in +'Best Tech Community' and 'Best Success Story' categories.

+

Unfortunately our submission into 'Best Success Story' has been pulled down! +We used that category to share the story from a dead open source project into +a thriving open source community with lots of users and contributors and to +highlight some of our milestones. Here's the short version:

+
    +
  • lots of technical updates and refactoring, latest everything, modern UI
    • +
  • the only open source test case management system on GitHub Marketplace
    • +
  • nearly 60000 downloads on Docker Hub
    • +
  • growing and active core team
    • +
  • active OSS contributors
    • +
+

Please help us gain more recognition:

+ +

Thanks you & happy testing!

+
+
-
-
- -

Kiwi TCMS 6.1.1

- - -

Posted by - Kiwi TCMS Team - on Mon 29 October 2018 -

-
- -
-

We're happy to announce Kiwi TCMS version 6.1.1! This release -squashes database migrations and removes -older migrations that have been squashed in previous releases, a few -improvements and bug fixes. -You can explore everything at -https://public.tenant.kiwitcms.org.

-

Supported upgrade paths:

-
-5.3   (or older) -> 5.3.1
-5.3.1 (or newer) -> 6.0.1
-6.0.1            -> 6.1
-6.1              -> 6.1.1
-
-

Docker images:

-
-kiwitcms/kiwi       latest  49fa42ddfe4d    955.7 MB
-kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955.7 MB
-kiwitcms/kiwi       6.1     b559123d25b0    970.2 MB
-kiwitcms/kiwi       6.0.1   87b24d94197d    970.1 MB
-kiwitcms/kiwi       5.3.1   a420465852be    976.8 MB
-
-
-

Changes since Kiwi TCMS 6.1

-
-

Improvements

-
    -
  • Dashboard will now show TestRuns which have test cases assigned to current -user. Fixes -Issue #520
    • -
  • API method TestRun.add_case() now returns a serialized TestCaseRun object. -Previously this method returned None
    • -
-
-
-

Bug fixes

-
    -
  • Don't show disabled Priority records in UI. Fixes -Issue #334
    • -
-
-
-

Translations

- -
-
-

Refactoring

-
    -
  • Fix some pylint errors (Ivaylo Ivanov)
    • -
-
-
-

Database

-
    -
  • Remove old squashed migrations for management, testplans, -testcases and testruns apps
    • -
  • Squash the remaining migrations for management, testplans, -testcases and testruns apps
    • -
-
-
-
-

How to upgrade

-

If you are using Kiwi TCMS as a Docker container then:

-
-cd Kiwi/
-git pull
-docker-compose down
-docker pull kiwitcms/kiwi
-docker pull centos/mariadb
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-
-

Don't forget to backup -before upgrade!

-
-
-

Subscription based online service

-

We are planning to convert -https://public.tenant.kiwitcms.org into -a subscription based service for people who don't want to bother installing -Kiwi TCMS on their own systems and just want to use it for test collaboration -with their team.

-

The income from this service will go towards covering operating costs and -supporting the -development team. Watch this -blog for further announcements about this. Meanwhile you may share your -thoughts via -Issue #515.

-
-
-

Plans to remove deprecated functionality

-

TestRun.product_version will be removed from the database schema in favor of -TestRun.plan.product_version! With the latest web interface it is not possible -to select a product version different than the one selected in the Test Plan. -Test runs should only be able to select product builds (after -Issue #246 is fixed).

diff --git a/blog/index8.html b/blog/index8.html index afb6a413..6777dcae 100644 --- a/blog/index8.html +++ b/blog/index8.html @@ -95,6 +95,121 @@

Blog

+
+
+ +

Kiwi TCMS 6.1.1

+ + +

Posted by + Kiwi TCMS Team + on Mon 29 October 2018 +

+
+ +
+

We're happy to announce Kiwi TCMS version 6.1.1! This release +squashes database migrations and removes +older migrations that have been squashed in previous releases, a few +improvements and bug fixes. +You can explore everything at +https://public.tenant.kiwitcms.org.

+

Supported upgrade paths:

+
+5.3   (or older) -> 5.3.1
+5.3.1 (or newer) -> 6.0.1
+6.0.1            -> 6.1
+6.1              -> 6.1.1
+
+

Docker images:

+
+kiwitcms/kiwi       latest  49fa42ddfe4d    955.7 MB
+kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955.7 MB
+kiwitcms/kiwi       6.1     b559123d25b0    970.2 MB
+kiwitcms/kiwi       6.0.1   87b24d94197d    970.1 MB
+kiwitcms/kiwi       5.3.1   a420465852be    976.8 MB
+
+
+

Changes since Kiwi TCMS 6.1

+
+

Improvements

+
    +
  • Dashboard will now show TestRuns which have test cases assigned to current +user. Fixes +Issue #520
    • +
  • API method TestRun.add_case() now returns a serialized TestCaseRun object. +Previously this method returned None
    • +
+
+
+

Bug fixes

+
    +
  • Don't show disabled Priority records in UI. Fixes +Issue #334
    • +
+
+
+

Translations

+ +
+
+

Refactoring

+
    +
  • Fix some pylint errors (Ivaylo Ivanov)
    • +
+
+
+

Database

+
    +
  • Remove old squashed migrations for management, testplans, +testcases and testruns apps
    • +
  • Squash the remaining migrations for management, testplans, +testcases and testruns apps
    • +
+
+
+
+

How to upgrade

+

If you are using Kiwi TCMS as a Docker container then:

+
+cd Kiwi/
+git pull
+docker-compose down
+docker pull kiwitcms/kiwi
+docker pull centos/mariadb
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+
+

Don't forget to backup +before upgrade!

+
+
+

Subscription based online service

+

We are planning to convert +https://public.tenant.kiwitcms.org into +a subscription based service for people who don't want to bother installing +Kiwi TCMS on their own systems and just want to use it for test collaboration +with their team.

+

The income from this service will go towards covering operating costs and +supporting the +development team. Watch this +blog for further announcements about this. Meanwhile you may share your +thoughts via +Issue #515.

+
+
+

Plans to remove deprecated functionality

+

TestRun.product_version will be removed from the database schema in favor of +TestRun.plan.product_version! With the latest web interface it is not possible +to select a product version different than the one selected in the Test Plan. +Test runs should only be able to select product builds (after +Issue #246 is fixed).

+
+ +
+
-
-
- -

Kiwi TCMS & tcms-api version 4.0.0

- - -

Posted by - Kiwi TCMS Team - on Sat 10 February 2018 -

-
- -
-

We're happy to announce Kiwi TCMS version 4.0.0 -and the corresponding tcms-api version 4.0.0! This is a very big release -which introduces tons of backwards incompatible changes to the RPC layer -as well as several bug-fixes and enhancements!

-

With this release Kiwi TCMS meets one of our -milestones for 2018! All XML-RPC -namespaces now match DB model names and the API client class names. Lots of -similar and duplicate methods were removed and existing ones were simplified. -We've also reduced code duplication and technical debth by 1 month -according to stats by CodeClimate.

-

IMPORTANT: this is also the first release to officially publish the -kiwitcms/kiwi image on Docker Hub!

-

WARNING: upgrading to Kiwi TCMS 4.0.0 means you will have to upgrade -the tcms-api client as well. None of the 4.x releases is compatible with -older releases due to the massive ammount of changes in the RPC layer.

-

Changes since Kiwi TCMS 3.50

-

Enhancements and bug fixes

-
    -
  • Upgrade to Django 2.0.2 which patches a security issue
    • -
  • Pin JIRA client version to 1.0.10. Fixes - Issue #195
    • -
  • Generate api-docs for model classes
    • -
  • Updated documentation for all RPC methods
    • -
  • Use Grappelli jQuery initialization, fixes popup windows
    • -
  • Unify RPC namespaces, API client class names and server-side model names. - Fixes Issue #153
    • -
-

Settings

-
    -
  • Remove ADMIN_PREFIX setting
    • -
-

RPC methods refactoring

-
    -
  • Remove Build.check_build, use Build.filter
    • -
  • Remove Build.get, use Build.filter
    • -
  • Remove Build.get_caseruns, use TestCaseRun.filter
    • -
  • -

    Remove Build.get_runs, use TestRun.filter

    -
    • -
  • -

    Rename Env.filter_groups, use Env.Group.filter

    -
    • -
  • Rename Env.filter_properties, use Env.Property.filter
    • -
  • -

    Rename Env.filter_values, use Env.Value.filter

    -
    • -
  • -

    Remove Product.add_component, use Component.create

    -
    • -
  • Remove Product.add_version, use Version.create
    • -
  • Remove Product.check_category, use Category.filter
    • -
  • Remove Product.check_component, use Component.filter
    • -
  • Remove Product.check_product, use Product.filter
    • -
  • Remove Product.filter_categories, use Category.filter
    • -
  • Remove Product.filter_components, use Component.filter
    • -
  • Remove Product.filter_versions, use Version.filter
    • -
  • Remove Product.get, use Product.filter
    • -
  • Remove Product.get_builds, use Build.filter
    • -
  • Remove Product.get_cases, use TestCase.filter
    • -
  • Remove Product.get_categories, use Category.filter
    • -
  • Remove Product.get_category, use Category.filter
    • -
  • Remove Product.get_component, use Component.filter
    • -
  • -

    Remove Product.update_component, use Component.update

    -
    • -
  • -

    Rename Tag.get_tags to Tag.filter

    -
    • -
  • -

    Remove TestCase.add_comment

    -
    • -
  • Update signature for TestCase.add_component
    • -
  • Update signature for TestCase.add_tag
    • -
  • Remove TestCase.add_to_run, use TestRun.add_case
    • -
  • Remove TestCase.attach_bug, use Bug.create
    • -
  • Remove TestCase.calculate_average_estimated_time
    • -
  • Remove TestCase.calculate_total_estimated_time
    • -
  • Remove TestCase.check_case_status, use TestCaseStatus.filter
    • -
  • Remove TestCase.check_priority, use Priority.filter
    • -
  • Update signature for TestCase.create, no longer accepts plan, - component and bug dict attributes. Instead use - TestPlan.add_case, TestCase.add_component and Bug.create
    • -
  • Remove TestCase.detach_bug, use Bug.remove
    • -
  • Remove TestCase.filter_count
    • -
  • Remove TestCase.get, use TestCase.filter
    • -
  • Remove TestCase.get_bugs, use Bug.filter({'case': ?})
    • -
  • Remove TestCase.get_bug_systems
    • -
  • Remove TestCase.get_case_status, use TestCaseStatus.filter
    • -
  • Update signature for TestCase.get_components
    • -
  • Remove TestCase.get_plans, use TestPlan.filter({'case': ?})
    • -
  • Remove TestCase.get_priority, use Priority.filter
    • -
  • Remove TestCase.get_tags, use Tag.filter({'case': ?})
    • -
  • Remove TestCase.get_text, use TestCase.filter
    • -
  • Remove TestCase.link_plan, use TestPlan.add_case
    • -
  • Rename TestCase.notification_add_cc to TestCase.add_notification_cc - and update signature
    • -
  • Rename TestCase.notification_get_cc_list to TestCase.get_notification_cc - and update signature
    • -
  • Rename TestCase.notification_remove_cc to TestCase.remove_notification_cc - and update signature
    • -
  • Update signature for TestCase.remove_component
    • -
  • Update signature for TestCase.remove_tag
    • -
  • Remove TestCase.store_text, use TestCase.update with - setup, breakdown, action and effect attributes in the parameter dict
    • -
  • -

    Remove TestCase.unlink_plan, use TestPlan.remove_case

    -
    • -
  • -

    Remove TestCasePlan.get

    -
    • -
  • -

    Remove TestCasePlan.update

    -
    • -
  • -

    Update TestCaseRun.add_comment to accept a single ID as first parameter

    -
    • -
  • Remove TestCaseRun.attach_bug, use Bug.create
    • -
  • Rename TestCaseRun.attach_log to TestCaseRun.add_log
    • -
  • Remove TestCaseRun.detach_bug, use Bug.remove
    • -
  • Rename TestCaseRun.detach_log to TestCaseRun.remove_log
    • -
  • Remove TestCaseRun.get, use TestCaseRun.filter
    • -
  • Remove TestCaseRun.get_bugs, use Bug.filter({'case_run': ?})
    • -
  • Remove TestCaseRun.get_case_run_status_by_name
    • -
  • -

    Update signature for TestCaseRun.update

    -
    • -
  • -

    Remove TestPlan.add_component

    -
    • -
  • Update signature for TestPlan.add_tag
    • -
  • Remove TestPlan.check_plan_type, use PlanType.filter
    • -
  • Remove TestPlan.filter_count
    • -
  • Remove TestPlan.get, use TestPlan.filter
    • -
  • Remove TestPlan.get_all_cases_tags
    • -
  • Remove TestPlan.get_components
    • -
  • Remove TestPlan.get_env_groups, use Env.Group.filter({'testplan': ?})
    • -
  • Remove TestPlan.get_plan_type, use PlanType.filter
    • -
  • Remove TestPlan.get_product, use Product.filter({'plan': ?})
    • -
  • Remove TestPlan.get_tags, use Tag.filter({'plan': ?})
    • -
  • Remove TestPlan.get_test_cases, use TestCase.filter({'plan': ?})
    • -
  • Remove TestPlan.get_test_runs, use TestRun.filter({'plan': ?})
    • -
  • Remove TestPlan.get_text, use TestPlan.filter
    • -
  • Rename TestPlan.link_env_value to TestPlan.add_env_value - and update signature
    • -
  • Remove TestPlan.remove_component
    • -
  • Update signature for TestPlan.remove_tag
    • -
  • Remove TestPlan.store_text, use TestPlan.update with - a text attribute in the parameter values
    • -
  • -

    Rename TestPlan.unlink_env_value to TestPlan.remove_env_value - and update signature

    -
    • -
  • -

    Rename TestRun.add_cases to TestRun.add_case and update signature

    -
    • -
  • Update signature for TestRun.add_tag
    • -
  • Update signature for TestRun.create, no longer accepts case - dict attribute. Instead use TestRun.add_case
    • -
  • Remove TestRun.filter_count
    • -
  • Remove TestRun.get, use TestRun.filter
    • -
  • Remove TestRun.get_bugs
    • -
  • Remove TestRun.get_env_values, use Env.Value.filter({'testrun': ?})
    • -
  • Remove TestRun.get_tags, use Tag.filter({'run': ?})
    • -
  • Rename TestRun.get_test_cases to TestRun.get_cases
    • -
  • Remove TestRun.get_test_case_runs, use TestCaseRun.filter({'run': ?})
    • -
  • Remove TestRun.get_test_plan, use TestPlan.filter({'run': ?})[0]
    • -
  • Rename TestRun.remove_cases to TestRun.remove_case and update signature
    • -
  • Update signature for TestRun.remove_tag
    • -
  • -

    Update signature for TestRun.update

    -
    • -
  • -

    Rename User.get to User.filter

    -
    • -
  • Rename User.join to User.join_group
    • -
  • Update signature for User.update
    • -
-

Models and database migrations

-
    -
  • Remove model TestEnvironment
    • -
  • Remove model TestEnvironmentCategory
    • -
  • Remove model TestEnvironmentElement
    • -
  • Remove model TestEnvironmentMap
    • -
  • Remove model TestEnvironmentProperty
    • -
  • Remove model TestPlanComponent
    • -
  • Remove TestPlan.get_text_with_version()
    • -
  • Remove TestRun.get_previous_or_next()
    • -
-

IMPORTANT: this release introduces new database migrations!

-

tcms-api changes since 1.5.1

-
    -
  • Make the code compatible with Kiwi TCMS XML-RPC v4.0.0
    • -
  • Rename Status to TestCaseRunStatus
    • -
  • Rename CaseRun to TestCaseRun
    • -
  • Remove PlanStatus, use TestPlan.is_active
    • -
  • Remove RunStatus, use TestRun.finished
    • -
  • Remove TestPlan.components container
    • -
  • Update signature for TestPlan. Now accept text kwarg in constructor - instead of document.
    • -
-

How to upgrade

-

If you are using Kiwi TCMS as a Docker container then

-
cd Kiwi/
-docker-compose down
-docker pull kiwitcms/kiwi
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-
- -

Happy testing!

diff --git a/blog/index9.html b/blog/index9.html index cee5062c..47d7e093 100644 --- a/blog/index9.html +++ b/blog/index9.html @@ -95,6 +95,232 @@

Blog

+
+
+ +

Kiwi TCMS & tcms-api version 4.0.0

+ + +

Posted by + Kiwi TCMS Team + on Sat 10 February 2018 +

+
+ +
+

We're happy to announce Kiwi TCMS version 4.0.0 +and the corresponding tcms-api version 4.0.0! This is a very big release +which introduces tons of backwards incompatible changes to the RPC layer +as well as several bug-fixes and enhancements!

+

With this release Kiwi TCMS meets one of our +milestones for 2018! All XML-RPC +namespaces now match DB model names and the API client class names. Lots of +similar and duplicate methods were removed and existing ones were simplified. +We've also reduced code duplication and technical debth by 1 month +according to stats by CodeClimate.

+

IMPORTANT: this is also the first release to officially publish the +kiwitcms/kiwi image on Docker Hub!

+

WARNING: upgrading to Kiwi TCMS 4.0.0 means you will have to upgrade +the tcms-api client as well. None of the 4.x releases is compatible with +older releases due to the massive ammount of changes in the RPC layer.

+

Changes since Kiwi TCMS 3.50

+

Enhancements and bug fixes

+
    +
  • Upgrade to Django 2.0.2 which patches a security issue
    • +
  • Pin JIRA client version to 1.0.10. Fixes + Issue #195
    • +
  • Generate api-docs for model classes
    • +
  • Updated documentation for all RPC methods
    • +
  • Use Grappelli jQuery initialization, fixes popup windows
    • +
  • Unify RPC namespaces, API client class names and server-side model names. + Fixes Issue #153
    • +
+

Settings

+
    +
  • Remove ADMIN_PREFIX setting
    • +
+

RPC methods refactoring

+
    +
  • Remove Build.check_build, use Build.filter
    • +
  • Remove Build.get, use Build.filter
    • +
  • Remove Build.get_caseruns, use TestCaseRun.filter
    • +
  • +

    Remove Build.get_runs, use TestRun.filter

    +
    • +
  • +

    Rename Env.filter_groups, use Env.Group.filter

    +
    • +
  • Rename Env.filter_properties, use Env.Property.filter
    • +
  • +

    Rename Env.filter_values, use Env.Value.filter

    +
    • +
  • +

    Remove Product.add_component, use Component.create

    +
    • +
  • Remove Product.add_version, use Version.create
    • +
  • Remove Product.check_category, use Category.filter
    • +
  • Remove Product.check_component, use Component.filter
    • +
  • Remove Product.check_product, use Product.filter
    • +
  • Remove Product.filter_categories, use Category.filter
    • +
  • Remove Product.filter_components, use Component.filter
    • +
  • Remove Product.filter_versions, use Version.filter
    • +
  • Remove Product.get, use Product.filter
    • +
  • Remove Product.get_builds, use Build.filter
    • +
  • Remove Product.get_cases, use TestCase.filter
    • +
  • Remove Product.get_categories, use Category.filter
    • +
  • Remove Product.get_category, use Category.filter
    • +
  • Remove Product.get_component, use Component.filter
    • +
  • +

    Remove Product.update_component, use Component.update

    +
    • +
  • +

    Rename Tag.get_tags to Tag.filter

    +
    • +
  • +

    Remove TestCase.add_comment

    +
    • +
  • Update signature for TestCase.add_component
    • +
  • Update signature for TestCase.add_tag
    • +
  • Remove TestCase.add_to_run, use TestRun.add_case
    • +
  • Remove TestCase.attach_bug, use Bug.create
    • +
  • Remove TestCase.calculate_average_estimated_time
    • +
  • Remove TestCase.calculate_total_estimated_time
    • +
  • Remove TestCase.check_case_status, use TestCaseStatus.filter
    • +
  • Remove TestCase.check_priority, use Priority.filter
    • +
  • Update signature for TestCase.create, no longer accepts plan, + component and bug dict attributes. Instead use + TestPlan.add_case, TestCase.add_component and Bug.create
    • +
  • Remove TestCase.detach_bug, use Bug.remove
    • +
  • Remove TestCase.filter_count
    • +
  • Remove TestCase.get, use TestCase.filter
    • +
  • Remove TestCase.get_bugs, use Bug.filter({'case': ?})
    • +
  • Remove TestCase.get_bug_systems
    • +
  • Remove TestCase.get_case_status, use TestCaseStatus.filter
    • +
  • Update signature for TestCase.get_components
    • +
  • Remove TestCase.get_plans, use TestPlan.filter({'case': ?})
    • +
  • Remove TestCase.get_priority, use Priority.filter
    • +
  • Remove TestCase.get_tags, use Tag.filter({'case': ?})
    • +
  • Remove TestCase.get_text, use TestCase.filter
    • +
  • Remove TestCase.link_plan, use TestPlan.add_case
    • +
  • Rename TestCase.notification_add_cc to TestCase.add_notification_cc + and update signature
    • +
  • Rename TestCase.notification_get_cc_list to TestCase.get_notification_cc + and update signature
    • +
  • Rename TestCase.notification_remove_cc to TestCase.remove_notification_cc + and update signature
    • +
  • Update signature for TestCase.remove_component
    • +
  • Update signature for TestCase.remove_tag
    • +
  • Remove TestCase.store_text, use TestCase.update with + setup, breakdown, action and effect attributes in the parameter dict
    • +
  • +

    Remove TestCase.unlink_plan, use TestPlan.remove_case

    +
    • +
  • +

    Remove TestCasePlan.get

    +
    • +
  • +

    Remove TestCasePlan.update

    +
    • +
  • +

    Update TestCaseRun.add_comment to accept a single ID as first parameter

    +
    • +
  • Remove TestCaseRun.attach_bug, use Bug.create
    • +
  • Rename TestCaseRun.attach_log to TestCaseRun.add_log
    • +
  • Remove TestCaseRun.detach_bug, use Bug.remove
    • +
  • Rename TestCaseRun.detach_log to TestCaseRun.remove_log
    • +
  • Remove TestCaseRun.get, use TestCaseRun.filter
    • +
  • Remove TestCaseRun.get_bugs, use Bug.filter({'case_run': ?})
    • +
  • Remove TestCaseRun.get_case_run_status_by_name
    • +
  • +

    Update signature for TestCaseRun.update

    +
    • +
  • +

    Remove TestPlan.add_component

    +
    • +
  • Update signature for TestPlan.add_tag
    • +
  • Remove TestPlan.check_plan_type, use PlanType.filter
    • +
  • Remove TestPlan.filter_count
    • +
  • Remove TestPlan.get, use TestPlan.filter
    • +
  • Remove TestPlan.get_all_cases_tags
    • +
  • Remove TestPlan.get_components
    • +
  • Remove TestPlan.get_env_groups, use Env.Group.filter({'testplan': ?})
    • +
  • Remove TestPlan.get_plan_type, use PlanType.filter
    • +
  • Remove TestPlan.get_product, use Product.filter({'plan': ?})
    • +
  • Remove TestPlan.get_tags, use Tag.filter({'plan': ?})
    • +
  • Remove TestPlan.get_test_cases, use TestCase.filter({'plan': ?})
    • +
  • Remove TestPlan.get_test_runs, use TestRun.filter({'plan': ?})
    • +
  • Remove TestPlan.get_text, use TestPlan.filter
    • +
  • Rename TestPlan.link_env_value to TestPlan.add_env_value + and update signature
    • +
  • Remove TestPlan.remove_component
    • +
  • Update signature for TestPlan.remove_tag
    • +
  • Remove TestPlan.store_text, use TestPlan.update with + a text attribute in the parameter values
    • +
  • +

    Rename TestPlan.unlink_env_value to TestPlan.remove_env_value + and update signature

    +
    • +
  • +

    Rename TestRun.add_cases to TestRun.add_case and update signature

    +
    • +
  • Update signature for TestRun.add_tag
    • +
  • Update signature for TestRun.create, no longer accepts case + dict attribute. Instead use TestRun.add_case
    • +
  • Remove TestRun.filter_count
    • +
  • Remove TestRun.get, use TestRun.filter
    • +
  • Remove TestRun.get_bugs
    • +
  • Remove TestRun.get_env_values, use Env.Value.filter({'testrun': ?})
    • +
  • Remove TestRun.get_tags, use Tag.filter({'run': ?})
    • +
  • Rename TestRun.get_test_cases to TestRun.get_cases
    • +
  • Remove TestRun.get_test_case_runs, use TestCaseRun.filter({'run': ?})
    • +
  • Remove TestRun.get_test_plan, use TestPlan.filter({'run': ?})[0]
    • +
  • Rename TestRun.remove_cases to TestRun.remove_case and update signature
    • +
  • Update signature for TestRun.remove_tag
    • +
  • +

    Update signature for TestRun.update

    +
    • +
  • +

    Rename User.get to User.filter

    +
    • +
  • Rename User.join to User.join_group
    • +
  • Update signature for User.update
    • +
+

Models and database migrations

+
    +
  • Remove model TestEnvironment
    • +
  • Remove model TestEnvironmentCategory
    • +
  • Remove model TestEnvironmentElement
    • +
  • Remove model TestEnvironmentMap
    • +
  • Remove model TestEnvironmentProperty
    • +
  • Remove model TestPlanComponent
    • +
  • Remove TestPlan.get_text_with_version()
    • +
  • Remove TestRun.get_previous_or_next()
    • +
+

IMPORTANT: this release introduces new database migrations!

+

tcms-api changes since 1.5.1

+
    +
  • Make the code compatible with Kiwi TCMS XML-RPC v4.0.0
    • +
  • Rename Status to TestCaseRunStatus
    • +
  • Rename CaseRun to TestCaseRun
    • +
  • Remove PlanStatus, use TestPlan.is_active
    • +
  • Remove RunStatus, use TestRun.finished
    • +
  • Remove TestPlan.components container
    • +
  • Update signature for TestPlan. Now accept text kwarg in constructor + instead of document.
    • +
+

How to upgrade

+

If you are using Kiwi TCMS as a Docker container then

+
cd Kiwi/
+docker-compose down
+docker pull kiwitcms/kiwi
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+
+ + +

Happy testing!

+
+
diff --git a/blog/kiwi-tcms-team/2024/11/05/important-changes-to-user-accounts-on-tenantkiwitcmsorg/index.html b/blog/kiwi-tcms-team/2024/11/05/important-changes-to-user-accounts-on-tenantkiwitcmsorg/index.html new file mode 100644 index 00000000..b8d2dd87 --- /dev/null +++ b/blog/kiwi-tcms-team/2024/11/05/important-changes-to-user-accounts-on-tenantkiwitcmsorg/index.html @@ -0,0 +1,227 @@ + + + + + Kiwi TCMS - Important changes to user accounts on *.tenant.kiwitcms.org + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

Important changes to user accounts on *.tenant.kiwitcms.org

+

which affects all users

+ +

+ Posted by + Kiwi TCMS Team + on Tue 05 November 2024 +

+ +
+

Hello testers, +starting today we are discontinuing the ability to register user +accounts on https://public.tenant.kiwitcms.org! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!

+

How does this affect users

+
    +
  • New account registrations via email+password are not possible anymore - use OAuth login
    • +
  • Existing users are able to login via OAuth and/or email+password - reset your password + if forgotten
    • +
  • New subscription purchases will create user accounts automatically - + reset your password before first login. + Note: existing subscribers already have accounts
    • +
  • Inviting new users to a Private Tenant, PLUGINS -> Tenant -> Invite users + will create user accounts automatically - reset your password before first login
    • +
+

Happy Testing!

+
+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+
+ +
+ + +
+
+ +
+
+ + +
+ + + + + + + + \ No newline at end of file diff --git a/blog/kiwi-tcms-team/index.html b/blog/kiwi-tcms-team/index.html index a5b4b0dc..e742839e 100644 --- a/blog/kiwi-tcms-team/index.html +++ b/blog/kiwi-tcms-team/index.html @@ -101,6 +101,48 @@

Articles by Kiwi TCMS Team

+
+
+ +

Important changes to user accounts on *.tenant.kiwitcms.org

+ + +

Posted by + Kiwi TCMS Team + on Tue 05 November 2024 +

+
+ +
+

Hello testers, +starting today we are discontinuing the ability to register user +accounts on https://public.tenant.kiwitcms.org! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!

+

How does this affect users

+
    +
  • New account registrations via email+password are not possible anymore - use OAuth login
    • +
  • Existing users are able to login via OAuth and/or email+password - reset your password + if forgotten
    • +
  • New subscription purchases will create user accounts automatically - + reset your password before first login. + Note: existing subscribers already have accounts
    • +
  • Inviting new users to a Private Tenant, PLUGINS -> Tenant -> Invite users + will create user accounts automatically - reset your password before first login
    • +
+

Happy Testing!

+
+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+
-
-
- -

Kiwi TCMS 12.5

- - -

Posted by - Kiwi TCMS Team - on Tue 04 July 2023 -

-
- -
-

We're happy to announce Kiwi TCMS version 12.5!

-

IMPORTANT: this is a small release which contains security related updates, -several improvements and new translations!

-

You can explore everything at -https://public.tenant.kiwitcms.org!

-
-

Supported upgrade paths:

-
-5.3   (or older) -> 5.3.1
-5.3.1 (or newer) -> 6.0.1
-6.0.1            -> 6.1
-6.1              -> 6.1.1
-6.1.1            -> 6.2 (or newer)
-
-
-

---

-
-

Upstream container images (x86_64):

-
-kiwitcms/kiwi   latest  9a689f9866d9    597MB
-
-
-

IMPORTANT: version tagged and multi-arch -container images are available only to -subscribers!

-
-

Changes since Kiwi TCMS 12.4

-
-

Security

-
    -
  • Update django from 4.2.2 to 4.2.3. Fixes -CVE-2023-36053 - -ReDoS vulnerability
    • -
  • Patch misconfigured HTTP headers allowing stored XSS execution. Fixes -CVE-2023-36809
    • -
  • Sanitize test plan name in tree_view_html() function to reduce the -opportunity for exploiting stored XSS vulnerabilities
    • -
  • Extend the list of file upload validators to reduce the opportunity for -exploiting stored XSS vulnerabilities
    • -
-
-
-

Improvements

-
    -
  • Update django-colorfield from 0.8.0 to 0.9.0
    • -
  • Update django-extensions from 3.2.1 to 3.2.3
    • -
  • Update django-simple-captcha from 0.5.17 to 0.5.18
    • -
  • Update django-tree-queries from 0.14.0 to 0.15.0
    • -
  • Update jira from 3.5.1 to 3.5.2
    • -
  • Update python-gitlab from 3.14.0 to 3.15.0
    • -
  • Small update to HEALTHCHECK command in container
    • -
  • Replace mysql with native mariadb commands for backup/restore
    • -
-
-
-

Refactoring and testing

-
    -
  • Update node_modules/eslint from 8.42.0 to 8.44.0
    • -
  • Update node_modules/eslint-plugin-n from 16.0.0 to 16.0.1
    • -
  • Update node_modules/webpack from 5.85.0 to 5.88.1
    • -
  • Update node_modules/webpack-cli from 5.1.3 to 5.1.4
    • -
  • Pin Selenium to 4.9.1 b/c of failures with 4.10.0
    • -
  • Add configuration for testing with reverse proxy
    • -
  • Assert that Nginx proxy doesn't strip response headers
    • -
  • Assert on the number of Content-Type headers for attachments
    • -
  • Update how we seed GitLab API token used for testing
    • -
-
-
-

Translations

- -
-
-
-

Kiwi TCMS Enterprise v12.5-mt

-
    -

  • Based on Kiwi TCMS v12.5

    -
    • -

  • Update django-python3-ldap from 0.15.4 to 0.15.5

    -
    • -

  • Install django-prometheus inside container

    -
    • -

  • Pin Selenium to 4.9.1 b/c of failures with 4.10.0

    -
    -

    Private images:

    -
    -quay.io/kiwitcms/version            12.5 (aarch64)          2349e3ea1b78    04 Jul 2023     606MB
-quay.io/kiwitcms/version            12.5 (x86_64)           9a689f9866d9    04 Jul 2023     597MB
-quay.io/kiwitcms/enterprise         12.5-mt (aarch64)       56634afe511a    04 Jul 2023     852MB
-quay.io/kiwitcms/enterprise         12.5-mt (x86_64)        cdfd6965ad4e    04 Jul 2023     841MB
-
    -
    -
    • -
-

IMPORTANT: version tagged, multi-arch and Enterprise -container images are available only to -subscribers!

-
-
-

How to upgrade

-

Backup first! -Then execute the commands:

-
-cd path/containing/docker-compose/
-docker-compose down
-docker-compose pull
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py upgrade
-
-

Refer to -our documentation -for more details!

-

Happy testing!

-

---

-

If you like what we're doing and how Kiwi TCMS supports various communities -please help us grow!

- -
- -
-

diff --git a/blog/kiwi-tcms-team/index2.html b/blog/kiwi-tcms-team/index2.html index f8c0ee66..c7d04ce6 100644 --- a/blog/kiwi-tcms-team/index2.html +++ b/blog/kiwi-tcms-team/index2.html @@ -101,6 +101,151 @@

Articles by Kiwi TCMS Team

+
+
+ +

Kiwi TCMS 12.5

+ + +

Posted by + Kiwi TCMS Team + on Tue 04 July 2023 +

+
+ +
+

We're happy to announce Kiwi TCMS version 12.5!

+

IMPORTANT: this is a small release which contains security related updates, +several improvements and new translations!

+

You can explore everything at +https://public.tenant.kiwitcms.org!

+
+

Supported upgrade paths:

+
+5.3   (or older) -> 5.3.1
+5.3.1 (or newer) -> 6.0.1
+6.0.1            -> 6.1
+6.1              -> 6.1.1
+6.1.1            -> 6.2 (or newer)
+
+
+

---

+
+

Upstream container images (x86_64):

+
+kiwitcms/kiwi   latest  9a689f9866d9    597MB
+
+
+

IMPORTANT: version tagged and multi-arch +container images are available only to +subscribers!

+
+

Changes since Kiwi TCMS 12.4

+
+

Security

+
    +
  • Update django from 4.2.2 to 4.2.3. Fixes +CVE-2023-36053 - +ReDoS vulnerability
    • +
  • Patch misconfigured HTTP headers allowing stored XSS execution. Fixes +CVE-2023-36809
    • +
  • Sanitize test plan name in tree_view_html() function to reduce the +opportunity for exploiting stored XSS vulnerabilities
    • +
  • Extend the list of file upload validators to reduce the opportunity for +exploiting stored XSS vulnerabilities
    • +
+
+
+

Improvements

+
    +
  • Update django-colorfield from 0.8.0 to 0.9.0
    • +
  • Update django-extensions from 3.2.1 to 3.2.3
    • +
  • Update django-simple-captcha from 0.5.17 to 0.5.18
    • +
  • Update django-tree-queries from 0.14.0 to 0.15.0
    • +
  • Update jira from 3.5.1 to 3.5.2
    • +
  • Update python-gitlab from 3.14.0 to 3.15.0
    • +
  • Small update to HEALTHCHECK command in container
    • +
  • Replace mysql with native mariadb commands for backup/restore
    • +
+
+
+

Refactoring and testing

+
    +
  • Update node_modules/eslint from 8.42.0 to 8.44.0
    • +
  • Update node_modules/eslint-plugin-n from 16.0.0 to 16.0.1
    • +
  • Update node_modules/webpack from 5.85.0 to 5.88.1
    • +
  • Update node_modules/webpack-cli from 5.1.3 to 5.1.4
    • +
  • Pin Selenium to 4.9.1 b/c of failures with 4.10.0
    • +
  • Add configuration for testing with reverse proxy
    • +
  • Assert that Nginx proxy doesn't strip response headers
    • +
  • Assert on the number of Content-Type headers for attachments
    • +
  • Update how we seed GitLab API token used for testing
    • +
+
+
+

Translations

+ +
+
+
+

Kiwi TCMS Enterprise v12.5-mt

+
    +

  • Based on Kiwi TCMS v12.5

    +
    • +

  • Update django-python3-ldap from 0.15.4 to 0.15.5

    +
    • +

  • Install django-prometheus inside container

    +
    • +

  • Pin Selenium to 4.9.1 b/c of failures with 4.10.0

    +
    +

    Private images:

    +
    +quay.io/kiwitcms/version            12.5 (aarch64)          2349e3ea1b78    04 Jul 2023     606MB
+quay.io/kiwitcms/version            12.5 (x86_64)           9a689f9866d9    04 Jul 2023     597MB
+quay.io/kiwitcms/enterprise         12.5-mt (aarch64)       56634afe511a    04 Jul 2023     852MB
+quay.io/kiwitcms/enterprise         12.5-mt (x86_64)        cdfd6965ad4e    04 Jul 2023     841MB
+
    +
    +
    • +
+

IMPORTANT: version tagged, multi-arch and Enterprise +container images are available only to +subscribers!

+
+
+

How to upgrade

+

Backup first! +Then execute the commands:

+
+cd path/containing/docker-compose/
+docker-compose down
+docker-compose pull
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py upgrade
+
+

Refer to +our documentation +for more details!

+

Happy testing!

+

---

+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us grow!

+ +
+ +
+
-
-
- -

New and updated subscription plans for Kiwi TCMS

- - -

Posted by - Kiwi TCMS Team - on Tue 01 March 2022 -

-
- -
-

An active Kiwi TCMS subscription ensures a sustainable future for -all open source software maintained by the Kiwi TCMS team and -provides its holder with access to software versions and certain -level services. Given recent changes to -private container credentials -we have refreshed our product and service definitions.

-

New Self Support subscription

-

This is an entry-level subscription which provides read-only access to version tagged -containers of upstream Kiwi TCMS. It is suitable for experimentation, -very small teams, development against Kiwi TCMS and convenience during upgrades.

-

You are free to use any older or future versions of Kiwi TCMS available from -the kiwitcms/version container repository!

-

This subscription plan is also available via -GitHub Marketplace.

-

Private Tenant

-

This is our most popular subscription type.

-

Starting today it also includes access -to the kiwitcms/version container repository! -This is suitable for teams who prefer to be hosting Kiwi TCMS on-premise instead of -using the namespace provided under *.tenant.kiwitcms.org.

-

This subscription plan is also available via -GitHub Marketplace.

-

Everything else remains the same!

-

Enterprise Subscription

-

This is Kiwi TCMS tailored towards on-premise deployments in larger organizations. -Starting today it also automatically includes 1x Private Tenant which can be used -for development or experiments.

-

Support availability has been extended by 2 hours in order to cover more geographic areas!

-

Future features coming to enterprise subscribers - -tools for provisioning of Kiwi TCMS inside cloud environments and aarch64 containers.

-

Price has been increased to 400 $/mo.

-

New Managed Hosting subscription

-

This new offering is designed for the organizations which don't want to bother with provisioning -containers, configuring DNS resolution, managing SSL certificates, regular upgrades and backups. -The Kiwi TCMS team can do all of this for you and provide a fully isolated instance inside AWS.

-

Support availability has been extended by 2 days, covering Saturday and Sunday. When necessary -Managed Hosting subscribers have the option for video conferences with their support contact.

-
-

All changes are effective immediately. Existing customers are granted access to everything -that's new while billing changes are not applied.

-

If you prefer the "free beer" version of -Kiwi TCMS it is available via docker pull kiwitcms/kiwi - free to use -and without any guarantees according to GPLv2.

-

Please consider subscribing and help us make Kiwi TCMS better!

-

Happy Testing!

-
-
Newer Posts diff --git a/blog/kiwi-tcms-team/index3.html b/blog/kiwi-tcms-team/index3.html index 9a756df2..c92e935b 100644 --- a/blog/kiwi-tcms-team/index3.html +++ b/blog/kiwi-tcms-team/index3.html @@ -101,6 +101,66 @@

Articles by Kiwi TCMS Team

+
+
+ +

New and updated subscription plans for Kiwi TCMS

+ + +

Posted by + Kiwi TCMS Team + on Tue 01 March 2022 +

+
+ +
+

An active Kiwi TCMS subscription ensures a sustainable future for +all open source software maintained by the Kiwi TCMS team and +provides its holder with access to software versions and certain +level services. Given recent changes to +private container credentials +we have refreshed our product and service definitions.

+

New Self Support subscription

+

This is an entry-level subscription which provides read-only access to version tagged +containers of upstream Kiwi TCMS. It is suitable for experimentation, +very small teams, development against Kiwi TCMS and convenience during upgrades.

+

You are free to use any older or future versions of Kiwi TCMS available from +the kiwitcms/version container repository!

+

This subscription plan is also available via +GitHub Marketplace.

+

Private Tenant

+

This is our most popular subscription type.

+

Starting today it also includes access +to the kiwitcms/version container repository! +This is suitable for teams who prefer to be hosting Kiwi TCMS on-premise instead of +using the namespace provided under *.tenant.kiwitcms.org.

+

This subscription plan is also available via +GitHub Marketplace.

+

Everything else remains the same!

+

Enterprise Subscription

+

This is Kiwi TCMS tailored towards on-premise deployments in larger organizations. +Starting today it also automatically includes 1x Private Tenant which can be used +for development or experiments.

+

Support availability has been extended by 2 hours in order to cover more geographic areas!

+

Future features coming to enterprise subscribers - +tools for provisioning of Kiwi TCMS inside cloud environments and aarch64 containers.

+

Price has been increased to 400 $/mo.

+

New Managed Hosting subscription

+

This new offering is designed for the organizations which don't want to bother with provisioning +containers, configuring DNS resolution, managing SSL certificates, regular upgrades and backups. +The Kiwi TCMS team can do all of this for you and provide a fully isolated instance inside AWS.

+

Support availability has been extended by 2 days, covering Saturday and Sunday. When necessary +Managed Hosting subscribers have the option for video conferences with their support contact.

+
+

All changes are effective immediately. Existing customers are granted access to everything +that's new while billing changes are not applied.

+

If you prefer the "free beer" version of +Kiwi TCMS it is available via docker pull kiwitcms/kiwi - free to use +and without any guarantees according to GPLv2.

+

Please consider subscribing and help us make Kiwi TCMS better!

+

Happy Testing!

+
+
-
-
-
- -

Kiwi TCMS 10.0

- - -

Posted by - Kiwi TCMS Team - on Tue 02 March 2021 -

-
- -
-

We're happy to announce Kiwi TCMS version 10.0!

-

IMPORTANT: this is a major release which includes backwards -incompatible API changes, new database fields, improvements, bug fixes, -translation updates, new tests and internal refactoring. -It is the ninth release to include contributions via our -open source bounty program.

-

This is also the first release after Kiwi TCMS reached 400K pulls -on Docker Hub! You can explore everything at -https://public.tenant.kiwitcms.org!

-

Supported upgrade paths:

-
-5.3   (or older) -> 5.3.1
-5.3.1 (or newer) -> 6.0.1
-6.0.1            -> 6.1
-6.1              -> 6.1.1
-6.1.1            -> 6.2 (or newer)
-
-

Docker images:

-
-kiwitcms/kiwi       latest  9f23186803d5    736 MB
-kiwitcms/kiwi       6.2     7870085ad415    957 MB
-kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955 MB
-kiwitcms/kiwi       6.1     b559123d25b0    970 MB
-kiwitcms/kiwi       6.0.1   87b24d94197d    970 MB
-kiwitcms/kiwi       5.3.1   a420465852be    976 MB
-
-
-

Changes since Kiwi TCMS 9.0

-
-

Security

-
    -
  • Update node_modules/marked from 1.2.7 to 2.0.1. Also fixes -SNYK-JS-MARKED-1070800
    • -
  • Update django from 3.1.5 to 3.1.7 for CVE-2021-3281 and CVE-2021-23336
    • -
-
-
-

Improvements

-
    -
  • Update bleach from 3.2.1 to 3.3.0
    • -
  • Update django-colorfield from 0.3.2 to 0.4.1
    • -
  • Update django-extensions from 3.1.0 to 3.1.1
    • -
  • Update markdown from 3.3.3 to 3.3.4
    • -
  • Update pygments from 2.7.4 to 2.8.0
    • -
  • Update python-gitlab from 2.5.0 to 2.6.0
    • -
  • Change ON/OFF button messages (Krum Petkov)
    • -
  • Automatically set test run to finished/not-finished depending on -the state of all executions. Closes -Issue #441
    • -
  • Allow assigning users from group admin page. Fixes -Issue #1844
    • -
  • Improve documentation around setting up devel environment
    • -
-
-
-

Database

-
    -
  • Add TestRun.planned_start and TestRun.planned_stop fields. Refs -Issue #1928 (Andreea Moraru)
    • -
  • Add TestExecution.start_date field. Refs -Issue #1924 (Anastasiya Uraleva)
    • -
  • Rename field TestExecution.close_date to TestExecution.stop_date (Anastasiya Uraleva)
    • -
-
-
-

API

-
-

Warning

-

This release changes how Kiwi TCMS serializes API results and thus -introduces multiple backwards incompatible changes.

-
-
-

Important

-

All .filter() methods now return distinct records!

-
-
    -
  • New method PlanType.create()
    • -
  • Method TestCase.add_component() now returns a serialized Component -instead of a serialized TestCase. Refs -Issue #2145
    • -
  • Methods Product.filter(), Product.create() and Product.update():
      -
    • change input parameter classification_id to classification - type int
      • -
    • change result field classification_id to classification - type int
      • -
    -
    • -
  • Method Category.filter() changes result field -product_id to product - type int
    • -
  • Methods Component.filter(), Component.create() and Component.update():
      -
    • change input parameter product_id to product - type int
      • -
    • change input parameter initial_owner_id to initial_owner - type int
      • -
    • change input parameter initial_qa_contact_id to initial_qa_contact - type int
      • -
    • change result field product_id to product - type int
      • -
    • change result field initial_owner_id to initial_owner - type int
      • -
    • change result field initial_qa_contact_id to initial_qa_contact - type int
      • -
    • adds result field cases - type int - a TestCase ID if this component is -attached to a test case
      • -
    -
    • -
  • Methods Version.filter() and Version.create():
      -
    • change input parameter product_id to product - type int
      • -
    • change result field product_id to product - type int
      • -
    -
    • -
  • Method Tag.filter() now returns additional fields: -bugs, case, plan and run which causes existing queries to -return similar records attached to different parent objects. Consumers of these -results should be updated
    • -
  • Methods TestPlan.filter(), TestPlan.create() and TestPlan.update():
      -
    • change input parameter author_id to author - type int
      • -
    • change input parameter parent_id to parent - type int
      • -
    • change input parameter product_id to product - type int
      • -
    • change input parameter product_version_id to product_version - type int
      • -
    • change input parameter type_id to type - type int
      • -
    • change result field author_id to author - type int
      • -
    • change result field parent_id to parent - type int
      • -
    • change result field product_id to product - type int
      • -
    • change result field product_version_id to product_version - type int
      • -
    • change result field type_id to type - type int
      • -
    • remove result fields cases, tag, default_product_version
      • -
    -
    • -
  • Method TestPlan.filter() -adds result fields product_version__value, product__name, -author__username and type__name
    • -
  • Methods TestRun.filter(), TestRun.create() and TestRun.update():
      -
    • change result field build_id to build - type int
      • -
    • change result field default_tester_id to default_tester - type int
      • -
    • change result field manager_id to manager - type int
      • -
    • change result field plan_id to plan - type int
      • -
    • change result field product_version_id to product_version - type int
      • -
    • remove result fields cc, tag
      • -
    -
    • -
  • Method TestRun.filter() adds result fields product_version__value, -plan__product, plan__name, build__name, manager__username and -default_tester__username
    • -
  • Methods TestExecution.filter() and TestExecution.update():
      -
    • change input parameter assigee_id to assignee - type int
      • -
    • change input parameter build_id to build - type int
      • -
    • change input parameter case_id to case - type int
      • -
    • change input parameter run_id to run - type int
      • -
    • change input parameter status_id to status - type int
      • -
    • change input parameter tested_by_id to tested_by - type int
      • -
    • change result field assigee_id to assignee - type int
      • -
    • change result field build_id to build - type int
      • -
    • change result field case_id to case - type int
      • -
    • change result field run_id to run - type int
      • -
    • change result field status_id to status - type int
      • -
    • change result field tested_by_id to tested_by - type int
      • -
    -
    • -
  • Method TestExecution.filter() adds result fields assignee__username, -tested_by__username, case__summary, build__name and status__name
    • -
  • Method TestExecution.get_links() change result field -execution_id to execution - type int
    • -
  • Method TestRun.add_case() changes result field names similarly to -TestExecution.filter() method
    • -
  • Methods TestCase.filter(), TestCase.create() and TestCase.update():
      -
    • change input parameter author_id to author - type int
      • -
    • change input parameter case_status_id to case_status - type int
      • -
    • change input parameter category_id to category - type int
      • -
    • change input parameter default_tester_id to default_tester - type int
      • -
    • change input parameter priority_id to priority - type int
      • -
    • change input parameter reviewer_id to reviewer - type int
      • -
    • change result field author_id to author - type int
      • -
    • change result field case_status_id to case_status - type int
      • -
    • change result field category_id to category - type int
      • -
    • change result field default_tester_id to default_tester - type int
      • -
    • change result field priority_id to priority - type int
      • -
    • change result field reviewer_id to reviewer - type int
      • -
    • remove result fields component, plan, tag
      • -
    -
    • -
  • Method TestCase.filter() adds result fields case_status__name, -category__name, priority__value, author__username, -default_tester__username and reviewer__username
    • -
  • Methods TestRun.get_cases() and TestPlan.add_case() change -result field names similarly to TestCase.filter() method
    • -
-
-
-

Bug fixes

-
    -
  • Fix removing a component from a test case immediately after it has been added. Fixes -Issue #2145 (Gagan Deep)
    • -
  • Fix broken object navigation in navbar. Fixes -Issue #991
    • -
  • Refactor search pages rendering to speed it up. Closes -Issue #1014
    • -
-
-
-

Refactoring & testing

-
    -
  • Update tests for TestRun.create() API method. Refs -Issue #1928 (Andreea Moraru)
    • -
  • Add automation tests. Closes -Issue #1618 (Mariyan Garvanski)
    • -
  • Add additional automation tests for tcms.management.admin. Closes -Issue #1610 (Gagan Deep)
    • -
  • Add additional automation tests for tcms.testcases.views.EditTestCaseView. Closes -Issue #1615 (Gagan Deep)
    • -
  • Add additional automation tests for tcms.kiwi_auth.forms. Closes -Issue #1609 (Kapil Bansal)
    • -
  • Change location of included HTML templates (Alexander Tsvetanov, Krum Petkov)
    • -
  • Erase unused view & templates (Alexander Tsvetanov)
    • -
  • Enable eslint. Closes -Issue #1281
    • -
  • Change how beakerlib test framework is installed to avoid problems -during integration tests
    • -
  • Better inspection of beakerlib test results to avoid false positive results
    • -
-
-
-

Translations

- -
-
-
-

Kiwi TCMS Enterprise v10.0-mt

-
    -
  • Based on Kiwi TCMS v10.0
    • -
  • Update kiwitcms-github-app from 1.2.2 to 1.2.4
    • -
  • Update kiwitcms-tenants from 1.4.2 to 1.4.3
    • -
  • Update django-python3-ldap from 0.11.3 to 0.11.4
    • -
-
-
-

Automation framework plugins

-

The following -test automation framework plugins -have been upgraded to work with Kiwi TCMS v10.0:

- -
-
-

How to upgrade

-

Backup first! -If you are using Kiwi TCMS as a Docker container then:

-
-cd path/containing/docker-compose/
-docker-compose down
-docker-compose pull
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-
-

Refer to -our documentation -for more details!

-

Happy testing!

-

---

-

If you like what we're doing and how Kiwi TCMS supports various communities -please help us!

-
diff --git a/blog/kiwi-tcms-team/index4.html b/blog/kiwi-tcms-team/index4.html index 86a5e1de..bf8de747 100644 --- a/blog/kiwi-tcms-team/index4.html +++ b/blog/kiwi-tcms-team/index4.html @@ -101,6 +101,296 @@

Articles by Kiwi TCMS Team

+
+
+ +

Kiwi TCMS 10.0

+ + +

Posted by + Kiwi TCMS Team + on Tue 02 March 2021 +

+
+ +
+

We're happy to announce Kiwi TCMS version 10.0!

+

IMPORTANT: this is a major release which includes backwards +incompatible API changes, new database fields, improvements, bug fixes, +translation updates, new tests and internal refactoring. +It is the ninth release to include contributions via our +open source bounty program.

+

This is also the first release after Kiwi TCMS reached 400K pulls +on Docker Hub! You can explore everything at +https://public.tenant.kiwitcms.org!

+

Supported upgrade paths:

+
+5.3   (or older) -> 5.3.1
+5.3.1 (or newer) -> 6.0.1
+6.0.1            -> 6.1
+6.1              -> 6.1.1
+6.1.1            -> 6.2 (or newer)
+
+

Docker images:

+
+kiwitcms/kiwi       latest  9f23186803d5    736 MB
+kiwitcms/kiwi       6.2     7870085ad415    957 MB
+kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955 MB
+kiwitcms/kiwi       6.1     b559123d25b0    970 MB
+kiwitcms/kiwi       6.0.1   87b24d94197d    970 MB
+kiwitcms/kiwi       5.3.1   a420465852be    976 MB
+
+
+

Changes since Kiwi TCMS 9.0

+
+

Security

+
    +
  • Update node_modules/marked from 1.2.7 to 2.0.1. Also fixes +SNYK-JS-MARKED-1070800
    • +
  • Update django from 3.1.5 to 3.1.7 for CVE-2021-3281 and CVE-2021-23336
    • +
+
+
+

Improvements

+
    +
  • Update bleach from 3.2.1 to 3.3.0
    • +
  • Update django-colorfield from 0.3.2 to 0.4.1
    • +
  • Update django-extensions from 3.1.0 to 3.1.1
    • +
  • Update markdown from 3.3.3 to 3.3.4
    • +
  • Update pygments from 2.7.4 to 2.8.0
    • +
  • Update python-gitlab from 2.5.0 to 2.6.0
    • +
  • Change ON/OFF button messages (Krum Petkov)
    • +
  • Automatically set test run to finished/not-finished depending on +the state of all executions. Closes +Issue #441
    • +
  • Allow assigning users from group admin page. Fixes +Issue #1844
    • +
  • Improve documentation around setting up devel environment
    • +
+
+
+

Database

+
    +
  • Add TestRun.planned_start and TestRun.planned_stop fields. Refs +Issue #1928 (Andreea Moraru)
    • +
  • Add TestExecution.start_date field. Refs +Issue #1924 (Anastasiya Uraleva)
    • +
  • Rename field TestExecution.close_date to TestExecution.stop_date (Anastasiya Uraleva)
    • +
+
+
+

API

+
+

Warning

+

This release changes how Kiwi TCMS serializes API results and thus +introduces multiple backwards incompatible changes.

+
+
+

Important

+

All .filter() methods now return distinct records!

+
+
    +
  • New method PlanType.create()
    • +
  • Method TestCase.add_component() now returns a serialized Component +instead of a serialized TestCase. Refs +Issue #2145
    • +
  • Methods Product.filter(), Product.create() and Product.update():
      +
    • change input parameter classification_id to classification - type int
      • +
    • change result field classification_id to classification - type int
      • +
    +
    • +
  • Method Category.filter() changes result field +product_id to product - type int
    • +
  • Methods Component.filter(), Component.create() and Component.update():
      +
    • change input parameter product_id to product - type int
      • +
    • change input parameter initial_owner_id to initial_owner - type int
      • +
    • change input parameter initial_qa_contact_id to initial_qa_contact - type int
      • +
    • change result field product_id to product - type int
      • +
    • change result field initial_owner_id to initial_owner - type int
      • +
    • change result field initial_qa_contact_id to initial_qa_contact - type int
      • +
    • adds result field cases - type int - a TestCase ID if this component is +attached to a test case
      • +
    +
    • +
  • Methods Version.filter() and Version.create():
      +
    • change input parameter product_id to product - type int
      • +
    • change result field product_id to product - type int
      • +
    +
    • +
  • Method Tag.filter() now returns additional fields: +bugs, case, plan and run which causes existing queries to +return similar records attached to different parent objects. Consumers of these +results should be updated
    • +
  • Methods TestPlan.filter(), TestPlan.create() and TestPlan.update():
      +
    • change input parameter author_id to author - type int
      • +
    • change input parameter parent_id to parent - type int
      • +
    • change input parameter product_id to product - type int
      • +
    • change input parameter product_version_id to product_version - type int
      • +
    • change input parameter type_id to type - type int
      • +
    • change result field author_id to author - type int
      • +
    • change result field parent_id to parent - type int
      • +
    • change result field product_id to product - type int
      • +
    • change result field product_version_id to product_version - type int
      • +
    • change result field type_id to type - type int
      • +
    • remove result fields cases, tag, default_product_version
      • +
    +
    • +
  • Method TestPlan.filter() +adds result fields product_version__value, product__name, +author__username and type__name
    • +
  • Methods TestRun.filter(), TestRun.create() and TestRun.update():
      +
    • change result field build_id to build - type int
      • +
    • change result field default_tester_id to default_tester - type int
      • +
    • change result field manager_id to manager - type int
      • +
    • change result field plan_id to plan - type int
      • +
    • change result field product_version_id to product_version - type int
      • +
    • remove result fields cc, tag
      • +
    +
    • +
  • Method TestRun.filter() adds result fields product_version__value, +plan__product, plan__name, build__name, manager__username and +default_tester__username
    • +
  • Methods TestExecution.filter() and TestExecution.update():
      +
    • change input parameter assigee_id to assignee - type int
      • +
    • change input parameter build_id to build - type int
      • +
    • change input parameter case_id to case - type int
      • +
    • change input parameter run_id to run - type int
      • +
    • change input parameter status_id to status - type int
      • +
    • change input parameter tested_by_id to tested_by - type int
      • +
    • change result field assigee_id to assignee - type int
      • +
    • change result field build_id to build - type int
      • +
    • change result field case_id to case - type int
      • +
    • change result field run_id to run - type int
      • +
    • change result field status_id to status - type int
      • +
    • change result field tested_by_id to tested_by - type int
      • +
    +
    • +
  • Method TestExecution.filter() adds result fields assignee__username, +tested_by__username, case__summary, build__name and status__name
    • +
  • Method TestExecution.get_links() change result field +execution_id to execution - type int
    • +
  • Method TestRun.add_case() changes result field names similarly to +TestExecution.filter() method
    • +
  • Methods TestCase.filter(), TestCase.create() and TestCase.update():
      +
    • change input parameter author_id to author - type int
      • +
    • change input parameter case_status_id to case_status - type int
      • +
    • change input parameter category_id to category - type int
      • +
    • change input parameter default_tester_id to default_tester - type int
      • +
    • change input parameter priority_id to priority - type int
      • +
    • change input parameter reviewer_id to reviewer - type int
      • +
    • change result field author_id to author - type int
      • +
    • change result field case_status_id to case_status - type int
      • +
    • change result field category_id to category - type int
      • +
    • change result field default_tester_id to default_tester - type int
      • +
    • change result field priority_id to priority - type int
      • +
    • change result field reviewer_id to reviewer - type int
      • +
    • remove result fields component, plan, tag
      • +
    +
    • +
  • Method TestCase.filter() adds result fields case_status__name, +category__name, priority__value, author__username, +default_tester__username and reviewer__username
    • +
  • Methods TestRun.get_cases() and TestPlan.add_case() change +result field names similarly to TestCase.filter() method
    • +
+
+
+

Bug fixes

+
    +
  • Fix removing a component from a test case immediately after it has been added. Fixes +Issue #2145 (Gagan Deep)
    • +
  • Fix broken object navigation in navbar. Fixes +Issue #991
    • +
  • Refactor search pages rendering to speed it up. Closes +Issue #1014
    • +
+
+
+

Refactoring & testing

+
    +
  • Update tests for TestRun.create() API method. Refs +Issue #1928 (Andreea Moraru)
    • +
  • Add automation tests. Closes +Issue #1618 (Mariyan Garvanski)
    • +
  • Add additional automation tests for tcms.management.admin. Closes +Issue #1610 (Gagan Deep)
    • +
  • Add additional automation tests for tcms.testcases.views.EditTestCaseView. Closes +Issue #1615 (Gagan Deep)
    • +
  • Add additional automation tests for tcms.kiwi_auth.forms. Closes +Issue #1609 (Kapil Bansal)
    • +
  • Change location of included HTML templates (Alexander Tsvetanov, Krum Petkov)
    • +
  • Erase unused view & templates (Alexander Tsvetanov)
    • +
  • Enable eslint. Closes +Issue #1281
    • +
  • Change how beakerlib test framework is installed to avoid problems +during integration tests
    • +
  • Better inspection of beakerlib test results to avoid false positive results
    • +
+
+
+

Translations

+ +
+
+
+

Kiwi TCMS Enterprise v10.0-mt

+
    +
  • Based on Kiwi TCMS v10.0
    • +
  • Update kiwitcms-github-app from 1.2.2 to 1.2.4
    • +
  • Update kiwitcms-tenants from 1.4.2 to 1.4.3
    • +
  • Update django-python3-ldap from 0.11.3 to 0.11.4
    • +
+
+
+

Automation framework plugins

+

The following +test automation framework plugins +have been upgraded to work with Kiwi TCMS v10.0:

+ +
+
+

How to upgrade

+

Backup first! +If you are using Kiwi TCMS as a Docker container then:

+
+cd path/containing/docker-compose/
+docker-compose down
+docker-compose pull
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+
+

Refer to +our documentation +for more details!

+

Happy testing!

+

---

+

If you like what we're doing and how Kiwi TCMS supports various communities +please help us!

+ +
+ +
+
-
-
- -

CfP: deployment, backup and upgrade best practices

- - -

Posted by - Kiwi TCMS Team - on Tue 07 July 2020 -

-
- -
-

Kiwi TCMS is opening a call for proposals: Tell us how do you deploy, backup and upgrade -your Kiwi TCMS containers? What environment do you use, how do you migrate data -or ensure the system is always up and running? How do you go about testing if a -newer version doesn't break the features that you use ? What best practices have -you identified that can help others?

-

We are going to collect your feedback and update the existing documentation.

-

Please submit your responses here: -https://docs.google.com/forms/d/e/1FAIpQLSe-kioT_e3UHwV5irwLroR2Jsk5oYM_Ls6acVeLVcBn7Kpt7Q/viewform. -All fields are optional, including your email address!

-

Thank you and happy testing!

-
-
Newer Posts diff --git a/blog/kiwi-tcms-team/index5.html b/blog/kiwi-tcms-team/index5.html index 11c3be68..754b2961 100644 --- a/blog/kiwi-tcms-team/index5.html +++ b/blog/kiwi-tcms-team/index5.html @@ -101,6 +101,31 @@

Articles by Kiwi TCMS Team

+
+
+ +

CfP: deployment, backup and upgrade best practices

+ + +

Posted by + Kiwi TCMS Team + on Tue 07 July 2020 +

+
+ +
+

Kiwi TCMS is opening a call for proposals: Tell us how do you deploy, backup and upgrade +your Kiwi TCMS containers? What environment do you use, how do you migrate data +or ensure the system is always up and running? How do you go about testing if a +newer version doesn't break the features that you use ? What best practices have +you identified that can help others?

+

We are going to collect your feedback and update the existing documentation.

+

Please submit your responses here: +https://docs.google.com/forms/d/e/1FAIpQLSe-kioT_e3UHwV5irwLroR2Jsk5oYM_Ls6acVeLVcBn7Kpt7Q/viewform. +All fields are optional, including your email address!

+

Thank you and happy testing!

+
+
-
-
- -

Kiwi TCMS is going to FOSDEM 2020

- - -

Posted by - Kiwi TCMS Team - on Tue 26 November 2019 -

-
- -
-

Stand at FOSDEM'19

-

Hello testers, Kiwi TCMS is going to FOSDEM 2020. -This is where you can find us:

-
    -
  • Fri Jan 31st: after 18:00 @ Delirium Café - - we are taking part of the FOSDEM Beer Event where all participants are invited. - Shout out with #KiwiTCMS on Twitter if you can't find us in the crowd
    • -
  • Sat Feb 1st: - Testing and Automation devroom - - we are proud to be co-hosting this devroom together with Linaro and SUSE. - CfP is open until Dec 10th 2019. Apply here!
    • -
  • Sun Feb 2nd: Open Source Test Management stand - - we will be together with our friends from SystemTestPortal and we are preparing - some real black-box testing for you!
    • -
-

We would like to meet with all of you and talk about software testing, test management and -test process organization. In case you are stuck for crazy ideas checkout -our project mission for inspiration.

-

Picture: FOSDEM'19 with Kiwi TCMS, ReportPortal & SystemTestPortal

-

Happy testing!

-
-
Newer Posts diff --git a/blog/kiwi-tcms-team/index6.html b/blog/kiwi-tcms-team/index6.html index 25500fb8..dfa2441c 100644 --- a/blog/kiwi-tcms-team/index6.html +++ b/blog/kiwi-tcms-team/index6.html @@ -101,6 +101,43 @@

Articles by Kiwi TCMS Team

+
+
+ +

Kiwi TCMS is going to FOSDEM 2020

+ + +

Posted by + Kiwi TCMS Team + on Tue 26 November 2019 +

+
+ +
+

Stand at FOSDEM'19

+

Hello testers, Kiwi TCMS is going to FOSDEM 2020. +This is where you can find us:

+
    +
  • Fri Jan 31st: after 18:00 @ Delirium Café - + we are taking part of the FOSDEM Beer Event where all participants are invited. + Shout out with #KiwiTCMS on Twitter if you can't find us in the crowd
    • +
  • Sat Feb 1st: + Testing and Automation devroom - + we are proud to be co-hosting this devroom together with Linaro and SUSE. + CfP is open until Dec 10th 2019. Apply here!
    • +
  • Sun Feb 2nd: Open Source Test Management stand - + we will be together with our friends from SystemTestPortal and we are preparing + some real black-box testing for you!
    • +
+

We would like to meet with all of you and talk about software testing, test management and +test process organization. In case you are stuck for crazy ideas checkout +our project mission for inspiration.

+

Picture: FOSDEM'19 with Kiwi TCMS, ReportPortal & SystemTestPortal

+

Happy testing!

+
+
-
-
- -

Kiwi TCMS 6.4

- - -

Posted by - Kiwi TCMS Team - on Mon 07 January 2019 -

-
- -
-

We're happy to announce Kiwi TCMS version 6.4! This is a security, -improvement and bug-fix update that includes new versions of Django, -Patternfly and other dependencies. You can explore everything at -https://public.tenant.kiwitcms.org!

-

Supported upgrade paths:

-
-5.3   (or older) -> 5.3.1
-5.3.1 (or newer) -> 6.0.1
-6.0.1            -> 6.1
-6.1              -> 6.1.1
-6.1.1            -> 6.2 (or newer)
-
-

Docker images:

-
-kiwitcms/kiwi       latest  39fcb88182bb    963.4 MB
-kiwitcms/kiwi       6.2     7870085ad415    957.6 MB
-kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955.7 MB
-kiwitcms/kiwi       6.1     b559123d25b0    970.2 MB
-kiwitcms/kiwi       6.0.1   87b24d94197d    970.1 MB
-kiwitcms/kiwi       5.3.1   a420465852be    976.8 MB
-
-
-

Changes since Kiwi TCMS 6.3

-
-

Security

-
    -
  • Update Django from 2.1.4 to 2.1.5, which deals with CVE-2019-3498: -Content spoofing possibility in the default 404 page
    • -
  • Update Patternfly to version 3.59.0, which deals with XSS issue in bootstrap. -See CVE-2018-14041
    • -
  • By default session cookies will expire after 24 hours. This can be controlled -via the SESSION_COOKIE_AGE setting. Fixes -Issue #556
    • -
-
-
-

Improvements

-
    -
  • Update mysqlclient from 1.3.13 to 1.3.14
    • -
  • Update python-gitlab from 1.6.0 to 1.7.0
    • -
  • Update django-simple-history from 2.5.1 to 2.6.0
    • -
  • Update pygithub from 1.43.3 to 1.43.4
    • -
  • New API method TestCase.remove(). Initially requested as -SO #53844380
    • -
  • Drop down select widges in Patternfly pages are now styled with -bootstrap-select giving them more consistent look and feel with -the rest of the page (Anton Sankov)
    • -
  • Create new TestPlan page now includes toggles to control notifications -and whether or not the test plan is active. This was previously available -only in edit page (Anton Sankov)
    • -
  • By default TestPlan notification toggles are turned on. Previously they -were off (Anton Sankov)
    • -
  • Create and Edit TestPlan pages now look the same (Anton Sankov)
    • -
  • Kiwi TCMS is now accepting donations via -Open Collective
    • -
-
-
-

Removed functionality

-
    -
  • Remove TestPlan page -> Run menu -> Add cases to run action. -This is the same as TestRun page -> Cases menu -> Add action
    • -
  • Legacy reports will be removed after 1st March 2019. Provide your -feedback in -Issue #657
    • -
  • The /run/ URL path has been merged with /runs/ due to configuration -refactoring. This may break your bookmarks or permalinks!
    • -
-
-
-

Bug fixes

-
    -
  • Don't traceback if markdown text is None. Originally reported as -SO #53662887
    • -
  • Show loading spinner when searching. Fixes -Issue #653
    • -
  • Quick fix: when viewing TestPlan cases make TC summary link to the test case. -Previously the summary column was a link to nowhere.
    • -
-
-
-

Translations

- -
-
-

Refactoring

-
    -
  • Pylint fixes
    • -
  • New and updated internal linters
    • -
  • Refactor testplans.views.new to class based view (Anton Sankov)
    • -
  • Refactor TestCase -> Bugs tab -> Remove to JSON-RPC. References -Issue #18
    • -
  • Refactor removeCaseRunBug() to JSON-RPC, References -Issue #18
    • -
  • Remove unused render_form() methods
    • -
  • Remove unnecessary string-to-int conversion (Ivaylo Ivanov)
    • -
  • Remove obsolete label fields. References -Issue #652 (Anton Sankov)
    • -
  • Remove JavaScript that duplicates requestOperationUponFilteredCases()
    • -
  • Remove QuerySetIterationProxy class - not used anymore
    • -
-
-
-
-

How to upgrade

-

If you are using Kiwi TCMS as a Docker container then:

-
-cd Kiwi/
-git pull
-docker-compose down
-docker pull kiwitcms/kiwi
-docker pull centos/mariadb
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-
-

Don't forget to backup -before upgrade!

-

WARNING: kiwitcms/kiwi:latest and docker-compose.yml will -always point to the latest available version! If you have to upgrade in steps, -e.g. between several intermediate releases, you have to modify the above workflow:

-
-# starting from an older Kiwi TCMS version
-docker-compose down
-docker pull kiwitcms/kiwi:<next_upgrade_version>
-edit docker-compose.yml to use kiwitcms/kiwi:<next_upgrade_version>
-docker-compose up -d
-docker exec -it kiwi_web /Kiwi/manage.py migrate
-# repeat until you have reached latest
-
-

Happy testing!

-
- -
-
Newer Posts diff --git a/blog/kiwi-tcms-team/index7.html b/blog/kiwi-tcms-team/index7.html index 8ab8ade5..9eeab9a2 100644 --- a/blog/kiwi-tcms-team/index7.html +++ b/blog/kiwi-tcms-team/index7.html @@ -101,6 +101,157 @@

Articles by Kiwi TCMS Team

+
+
+ +

Kiwi TCMS 6.4

+ + +

Posted by + Kiwi TCMS Team + on Mon 07 January 2019 +

+
+ +
+

We're happy to announce Kiwi TCMS version 6.4! This is a security, +improvement and bug-fix update that includes new versions of Django, +Patternfly and other dependencies. You can explore everything at +https://public.tenant.kiwitcms.org!

+

Supported upgrade paths:

+
+5.3   (or older) -> 5.3.1
+5.3.1 (or newer) -> 6.0.1
+6.0.1            -> 6.1
+6.1              -> 6.1.1
+6.1.1            -> 6.2 (or newer)
+
+

Docker images:

+
+kiwitcms/kiwi       latest  39fcb88182bb    963.4 MB
+kiwitcms/kiwi       6.2     7870085ad415    957.6 MB
+kiwitcms/kiwi       6.1.1   49fa42ddfe4d    955.7 MB
+kiwitcms/kiwi       6.1     b559123d25b0    970.2 MB
+kiwitcms/kiwi       6.0.1   87b24d94197d    970.1 MB
+kiwitcms/kiwi       5.3.1   a420465852be    976.8 MB
+
+
+

Changes since Kiwi TCMS 6.3

+
+

Security

+
    +
  • Update Django from 2.1.4 to 2.1.5, which deals with CVE-2019-3498: +Content spoofing possibility in the default 404 page
    • +
  • Update Patternfly to version 3.59.0, which deals with XSS issue in bootstrap. +See CVE-2018-14041
    • +
  • By default session cookies will expire after 24 hours. This can be controlled +via the SESSION_COOKIE_AGE setting. Fixes +Issue #556
    • +
+
+
+

Improvements

+
    +
  • Update mysqlclient from 1.3.13 to 1.3.14
    • +
  • Update python-gitlab from 1.6.0 to 1.7.0
    • +
  • Update django-simple-history from 2.5.1 to 2.6.0
    • +
  • Update pygithub from 1.43.3 to 1.43.4
    • +
  • New API method TestCase.remove(). Initially requested as +SO #53844380
    • +
  • Drop down select widges in Patternfly pages are now styled with +bootstrap-select giving them more consistent look and feel with +the rest of the page (Anton Sankov)
    • +
  • Create new TestPlan page now includes toggles to control notifications +and whether or not the test plan is active. This was previously available +only in edit page (Anton Sankov)
    • +
  • By default TestPlan notification toggles are turned on. Previously they +were off (Anton Sankov)
    • +
  • Create and Edit TestPlan pages now look the same (Anton Sankov)
    • +
  • Kiwi TCMS is now accepting donations via +Open Collective
    • +
+
+
+

Removed functionality

+
    +
  • Remove TestPlan page -> Run menu -> Add cases to run action. +This is the same as TestRun page -> Cases menu -> Add action
    • +
  • Legacy reports will be removed after 1st March 2019. Provide your +feedback in +Issue #657
    • +
  • The /run/ URL path has been merged with /runs/ due to configuration +refactoring. This may break your bookmarks or permalinks!
    • +
+
+
+

Bug fixes

+
    +
  • Don't traceback if markdown text is None. Originally reported as +SO #53662887
    • +
  • Show loading spinner when searching. Fixes +Issue #653
    • +
  • Quick fix: when viewing TestPlan cases make TC summary link to the test case. +Previously the summary column was a link to nowhere.
    • +
+
+
+

Translations

+ +
+
+

Refactoring

+
    +
  • Pylint fixes
    • +
  • New and updated internal linters
    • +
  • Refactor testplans.views.new to class based view (Anton Sankov)
    • +
  • Refactor TestCase -> Bugs tab -> Remove to JSON-RPC. References +Issue #18
    • +
  • Refactor removeCaseRunBug() to JSON-RPC, References +Issue #18
    • +
  • Remove unused render_form() methods
    • +
  • Remove unnecessary string-to-int conversion (Ivaylo Ivanov)
    • +
  • Remove obsolete label fields. References +Issue #652 (Anton Sankov)
    • +
  • Remove JavaScript that duplicates requestOperationUponFilteredCases()
    • +
  • Remove QuerySetIterationProxy class - not used anymore
    • +
+
+
+
+

How to upgrade

+

If you are using Kiwi TCMS as a Docker container then:

+
+cd Kiwi/
+git pull
+docker-compose down
+docker pull kiwitcms/kiwi
+docker pull centos/mariadb
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+
+

Don't forget to backup +before upgrade!

+

WARNING: kiwitcms/kiwi:latest and docker-compose.yml will +always point to the latest available version! If you have to upgrade in steps, +e.g. between several intermediate releases, you have to modify the above workflow:

+
+# starting from an older Kiwi TCMS version
+docker-compose down
+docker pull kiwitcms/kiwi:<next_upgrade_version>
+edit docker-compose.yml to use kiwitcms/kiwi:<next_upgrade_version>
+docker-compose up -d
+docker exec -it kiwi_web /Kiwi/manage.py migrate
+# repeat until you have reached latest
+
+

Happy testing!

+
+ +
+
-
-
- -

Kiwi TCMS roadmap for 2018

- - -

Posted by - Kiwi TCMS Team - on Mon 22 January 2018 -

-
- -
-

Hello everyone. As you know Kiwi TCMS has been around for a while and it has -gone through some big changes in the last year! It started as an abandoned -Django 1.6 project with broken test suite and is now currently running on the -latest Django 2.0.1 with Python 3.5! It is clearly a legacy code base!

-

We, the Kiwi TCMS team, have learned a lot more about the project and this -blog post describes our roadmap for 2018 in terms of technical work and community -engagement. The general technical direction is cleaner/simpler code, -improved UI/UX and more tests!

-

Make code easier to maintain

-

The current code is a bunch of very large modules and functions and classes -bundled together. It is also old and sometimes looks like spaghetti code. -CodeClimate gives us a "D" rating -for maintainability with a 1 year estimated effort to fix that. There are 600+ -code smells and 600+ duplications detected by CodeClimate. Our goal is to get this -number down to zero!

-

Use pylint and pylint-django

-

pylint is the standard static analyzer for Python and currently it reports over -4000 errors and warnings when executed against Kiwi TCMS. This is a huge number and -it needs to become zero! We've also identified interesting patterns that will -make it into pylint and pylint-django plugins!

-

Render HTML, return JSON

-

The current state of affairs is a mix and match of everything. There are views that -render HTML, others which return pure JSON, other which return HTML encoded as JSON string -and probably everything in between. Views that render pages need to do just that -and views that are used with AJAX calls from the UI need to return pure JSON! -A lot of these are hiding in plain sight and will come to light when we start -overhauling the user interface.

-

Submit forms, post JSON, GET clean URLs

-

There are lots of forms in Kiwi TCMS. Sometimes they are submitted by the user and -other times they are serialized and POSTed by some JavaScript code. This isn't -very easy to understand plus this entire home-grown utility code doesn't bring -anything useful to the project. All of these need to be identified and cleaned up. -JavaScript code needs to send or consume JSON, nothing else!

-

There are also lots of places where Kiwi issues GET requests with a number of -query parameters. Our goal is to minimize these and where possible have the -parameters as part of the Django urls scheme, not as query strings.

-

API layer

-

The current API module is a bit disorganized. API namespaces don't match the -names of the underlying DB models and the API client classes don't match any -of the other two! The way we pass parameters and what these parameters are -named should match between the client, the RPC method and the underlying model!

-

In earlier releases we've removed duplicate or similar RPC methods and we -think there are more of these that need our love.

-

Documentation

-

We've started producing documentation from doc-strings and most of the RPC -methods have such. However it is unformatted and barely readable, sometimes -even inaccurate. Previous releases made progress on this but there's a lot -more to cover.

-

All RPC methods should be documented first and then the rest of Kiwi's -internals to make development easier!

-

No vendored JavaScript libraries

-

There are 11 vendored-in JavaScript files that we carry around in Kiwi TCMS. -Most notable are jQuery plus a few addons and Handlebars.js. To the extent possible -our goal is to use jQuery provided by Django or installed via NPM dependencies!

-

Less HTML templates with better organization

-

There are over 100 HTML templates in Kiwi TCMS. There are also email and even -JavaScript templates. For example there are get_cases.html and get_review_cases.html -which are essentially the same. This is kind of also true for templates used in -new and edit views! Such templates should be unified!

-

Those JavaScript templates need to be totally gone!

-

All templates are stuffed together in a single directory and their names -are not very predictable. They need to be split per application and follow -some kind of naming convention.

-

Modern interface with Patternfly

-

The UI already uses the Patternfly library for some of its widgets. Most notably -the main navigation header. Our goal is for the entire UI to be ported to Patternfly -by updating widgets HTML and CSS where needed. -This will also help clean things up a lot. At the same time we'll be rethinking how -information is organized on screen and how the person interacts with it! Usability -suggestions are very welcome!

-

This move will also help us get rid of the Handlebars dependency which is now -used for pop-up dialogs.

-

JavaScript updates and front-end testing

-

There's lots of JavaScript code on the front-end and honestly we don't quite know -what it does or how it is organized. There are also no tests on the front-end -whatsoever!

-

It is our goal for this to change with the intention to not overdo the JavaScript -part and keep things very minimal. At the moment we're thinking about vanilla jQuery -that will act as a proxy between the browser and the back-end!

-

Community efforts

-

A year ago hardly anybody knew what Kiwi TCMS was, the project didn't even have -this name, there was 1 active contributor and hardly any users! Now the community -has started to slowly revitalize, we're seeing some contributions from our -junior team members (more on this in another blog post) and also seeing -folks installing and using Kiwi TCMS and reporting interesting bugs and feature -requests around it!

-

For the upcoming year our goal is to seek active engagement with other open source -projects that could make use of Kiwi TCMS and work with them. Kudos to -openSUSE for being the first -to propose such integration! -We're also planning couple of appearances at a few conferences but there's -nothing confirmed yet.

-

Every other contribution in terms of bug reports, new users and feature requests -is of course welcome but we're very conscious of the fact that there's tons -of work to be done and the team is still very small!

-

Team wise we'd like to get the existing team members up to speed and tackle -the above tasks with priority. This will also help us introduce bug fixes -and new features more quickly!

Happy testing!

diff --git a/blog/kiwi-tcms-team/index8.html b/blog/kiwi-tcms-team/index8.html index 9acc2aee..f4b56e09 100644 --- a/blog/kiwi-tcms-team/index8.html +++ b/blog/kiwi-tcms-team/index8.html @@ -101,6 +101,120 @@

Articles by Kiwi TCMS Team

+
+
+ +

Kiwi TCMS roadmap for 2018

+ + +

Posted by + Kiwi TCMS Team + on Mon 22 January 2018 +

+
+ +
+

Hello everyone. As you know Kiwi TCMS has been around for a while and it has +gone through some big changes in the last year! It started as an abandoned +Django 1.6 project with broken test suite and is now currently running on the +latest Django 2.0.1 with Python 3.5! It is clearly a legacy code base!

+

We, the Kiwi TCMS team, have learned a lot more about the project and this +blog post describes our roadmap for 2018 in terms of technical work and community +engagement. The general technical direction is cleaner/simpler code, +improved UI/UX and more tests!

+

Make code easier to maintain

+

The current code is a bunch of very large modules and functions and classes +bundled together. It is also old and sometimes looks like spaghetti code. +CodeClimate gives us a "D" rating +for maintainability with a 1 year estimated effort to fix that. There are 600+ +code smells and 600+ duplications detected by CodeClimate. Our goal is to get this +number down to zero!

+

Use pylint and pylint-django

+

pylint is the standard static analyzer for Python and currently it reports over +4000 errors and warnings when executed against Kiwi TCMS. This is a huge number and +it needs to become zero! We've also identified interesting patterns that will +make it into pylint and pylint-django plugins!

+

Render HTML, return JSON

+

The current state of affairs is a mix and match of everything. There are views that +render HTML, others which return pure JSON, other which return HTML encoded as JSON string +and probably everything in between. Views that render pages need to do just that +and views that are used with AJAX calls from the UI need to return pure JSON! +A lot of these are hiding in plain sight and will come to light when we start +overhauling the user interface.

+

Submit forms, post JSON, GET clean URLs

+

There are lots of forms in Kiwi TCMS. Sometimes they are submitted by the user and +other times they are serialized and POSTed by some JavaScript code. This isn't +very easy to understand plus this entire home-grown utility code doesn't bring +anything useful to the project. All of these need to be identified and cleaned up. +JavaScript code needs to send or consume JSON, nothing else!

+

There are also lots of places where Kiwi issues GET requests with a number of +query parameters. Our goal is to minimize these and where possible have the +parameters as part of the Django urls scheme, not as query strings.

+

API layer

+

The current API module is a bit disorganized. API namespaces don't match the +names of the underlying DB models and the API client classes don't match any +of the other two! The way we pass parameters and what these parameters are +named should match between the client, the RPC method and the underlying model!

+

In earlier releases we've removed duplicate or similar RPC methods and we +think there are more of these that need our love.

+

Documentation

+

We've started producing documentation from doc-strings and most of the RPC +methods have such. However it is unformatted and barely readable, sometimes +even inaccurate. Previous releases made progress on this but there's a lot +more to cover.

+

All RPC methods should be documented first and then the rest of Kiwi's +internals to make development easier!

+

No vendored JavaScript libraries

+

There are 11 vendored-in JavaScript files that we carry around in Kiwi TCMS. +Most notable are jQuery plus a few addons and Handlebars.js. To the extent possible +our goal is to use jQuery provided by Django or installed via NPM dependencies!

+

Less HTML templates with better organization

+

There are over 100 HTML templates in Kiwi TCMS. There are also email and even +JavaScript templates. For example there are get_cases.html and get_review_cases.html +which are essentially the same. This is kind of also true for templates used in +new and edit views! Such templates should be unified!

+

Those JavaScript templates need to be totally gone!

+

All templates are stuffed together in a single directory and their names +are not very predictable. They need to be split per application and follow +some kind of naming convention.

+

Modern interface with Patternfly

+

The UI already uses the Patternfly library for some of its widgets. Most notably +the main navigation header. Our goal is for the entire UI to be ported to Patternfly +by updating widgets HTML and CSS where needed. +This will also help clean things up a lot. At the same time we'll be rethinking how +information is organized on screen and how the person interacts with it! Usability +suggestions are very welcome!

+

This move will also help us get rid of the Handlebars dependency which is now +used for pop-up dialogs.

+

JavaScript updates and front-end testing

+

There's lots of JavaScript code on the front-end and honestly we don't quite know +what it does or how it is organized. There are also no tests on the front-end +whatsoever!

+

It is our goal for this to change with the intention to not overdo the JavaScript +part and keep things very minimal. At the moment we're thinking about vanilla jQuery +that will act as a proxy between the browser and the back-end!

+

Community efforts

+

A year ago hardly anybody knew what Kiwi TCMS was, the project didn't even have +this name, there was 1 active contributor and hardly any users! Now the community +has started to slowly revitalize, we're seeing some contributions from our +junior team members (more on this in another blog post) and also seeing +folks installing and using Kiwi TCMS and reporting interesting bugs and feature +requests around it!

+

For the upcoming year our goal is to seek active engagement with other open source +projects that could make use of Kiwi TCMS and work with them. Kudos to +openSUSE for being the first +to propose such integration! +We're also planning couple of appearances at a few conferences but there's +nothing confirmed yet.

+

Every other contribution in terms of bug reports, new users and feature requests +is of course welcome but we're very conscious of the fact that there's tons +of work to be done and the team is still very small!

+

Team wise we'd like to get the existing team members up to speed and tackle +the above tasks with priority. This will also help us introduce bug fixes +and new features more quickly!

+

Happy testing!

+
+
diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml index 5a6b6172..ae31a732 100644 --- a/feeds/all.atom.xml +++ b/feeds/all.atom.xml @@ -1,5 +1,37 @@ -Kiwi TCMS/2024-10-29T10:00:00+02:00Testing and Continuous Delivery devroom, FOSDEM'252024-10-29T10:00:00+02:002024-10-29T10:00:00+02:00Kiwi TCMS Teamtag:None,2024-10-29:/blog/kiwi-tcms-team/2024/10/29/testing-and-continuous-delivery-devroom-fosdem25/<p><img alt="&quot;Cfp banner&quot;" src="/images/fosdem/2025/banner.png" title="Cfp banner"></p> +Kiwi TCMS/2024-11-05T22:45:00+02:00Important changes to user accounts on *.tenant.kiwitcms.org2024-11-05T22:45:00+02:002024-11-05T22:45:00+02:00Kiwi TCMS Teamtag:None,2024-11-05:/blog/kiwi-tcms-team/2024/11/05/important-changes-to-user-accounts-on-tenantkiwitcmsorg/<p>Hello testers, +starting today we are discontinuing the ability to register user +accounts on <a href="https://public.tenant.kiwitcms.org">https://public.tenant.kiwitcms.org</a>! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!</p> +<h2>How does this affect users</h2> +<ul> +<li>New account registrations via email+password are not …</li></ul><p>Hello testers, +starting today we are discontinuing the ability to register user +accounts on <a href="https://public.tenant.kiwitcms.org">https://public.tenant.kiwitcms.org</a>! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!</p> +<h2>How does this affect users</h2> +<ul> +<li>New account registrations via email+password are not possible anymore - use OAuth login</li> +<li>Existing users are able to login via OAuth and/or email+password - reset your password + if forgotten</li> +<li>New subscription purchases will create user accounts automatically - + reset your password before first login. + <em>Note: existing subscribers already have accounts</em></li> +<li>Inviting new users to a Private Tenant, <code>PLUGINS -&gt; Tenant -&gt; Invite users</code> + will create user accounts automatically - reset your password before first login</li> +</ul> +<p>Happy Testing!</p> +<hr> +<p>If you like what we're doing and how Kiwi TCMS supports various communities +please help us!</p> +<ul> +<li><a href="https://github.com/kiwitcms/Kiwi/stargazers">Give ⭐ on GitHub</a>;</li> +<li><a href="https://gitlab.com/gitlab-org/gitlab/-/issues/334558">Give 👍 on GitLab</a>;</li> +<li><a href="https://kiwitcms.us17.list-manage.com/subscribe/post?u=9b57a21155a3b7c655ae8f922&amp;id=c970a37581">Join our newsletter</a> + and follow all project news;</li> +<li><a href="https://kiwitcms.readthedocs.io/en/latest/contribution.html">Become a contributor</a> and an awesome open source hacker;</li> +<li><a href="/#subscriptions">Become a customer</a> and help us sustain development</li> +</ul>Testing and Continuous Delivery devroom, FOSDEM'252024-10-29T10:00:00+02:002024-10-29T10:00:00+02:00Kiwi TCMS Teamtag:None,2024-10-29:/blog/kiwi-tcms-team/2024/10/29/testing-and-continuous-delivery-devroom-fosdem25/<p><img alt="&quot;Cfp banner&quot;" src="/images/fosdem/2025/banner.png" title="Cfp banner"></p> <p>Attention testers! On behalf of the <a href="https://fosdem-testingautomation.github.io/"><em>Testing and Continuous Delivery devroom</em></a> we'd like to announce that call for participation is now open. diff --git a/feeds/misc.atom.xml b/feeds/misc.atom.xml index ad48e055..be5e423e 100644 --- a/feeds/misc.atom.xml +++ b/feeds/misc.atom.xml @@ -1,5 +1,37 @@ -Kiwi TCMS - misc/2024-10-29T10:00:00+02:00Testing and Continuous Delivery devroom, FOSDEM'252024-10-29T10:00:00+02:002024-10-29T10:00:00+02:00Kiwi TCMS Teamtag:None,2024-10-29:/blog/kiwi-tcms-team/2024/10/29/testing-and-continuous-delivery-devroom-fosdem25/<p><img alt="&quot;Cfp banner&quot;" src="/images/fosdem/2025/banner.png" title="Cfp banner"></p> +Kiwi TCMS - misc/2024-11-05T22:45:00+02:00Important changes to user accounts on *.tenant.kiwitcms.org2024-11-05T22:45:00+02:002024-11-05T22:45:00+02:00Kiwi TCMS Teamtag:None,2024-11-05:/blog/kiwi-tcms-team/2024/11/05/important-changes-to-user-accounts-on-tenantkiwitcmsorg/<p>Hello testers, +starting today we are discontinuing the ability to register user +accounts on <a href="https://public.tenant.kiwitcms.org">https://public.tenant.kiwitcms.org</a>! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!</p> +<h2>How does this affect users</h2> +<ul> +<li>New account registrations via email+password are not …</li></ul><p>Hello testers, +starting today we are discontinuing the ability to register user +accounts on <a href="https://public.tenant.kiwitcms.org">https://public.tenant.kiwitcms.org</a>! New accounts can still +be created by logging in via the existing OAuth integrations - GitHub, GitLab and Google!</p> +<h2>How does this affect users</h2> +<ul> +<li>New account registrations via email+password are not possible anymore - use OAuth login</li> +<li>Existing users are able to login via OAuth and/or email+password - reset your password + if forgotten</li> +<li>New subscription purchases will create user accounts automatically - + reset your password before first login. + <em>Note: existing subscribers already have accounts</em></li> +<li>Inviting new users to a Private Tenant, <code>PLUGINS -&gt; Tenant -&gt; Invite users</code> + will create user accounts automatically - reset your password before first login</li> +</ul> +<p>Happy Testing!</p> +<hr> +<p>If you like what we're doing and how Kiwi TCMS supports various communities +please help us!</p> +<ul> +<li><a href="https://github.com/kiwitcms/Kiwi/stargazers">Give ⭐ on GitHub</a>;</li> +<li><a href="https://gitlab.com/gitlab-org/gitlab/-/issues/334558">Give 👍 on GitLab</a>;</li> +<li><a href="https://kiwitcms.us17.list-manage.com/subscribe/post?u=9b57a21155a3b7c655ae8f922&amp;id=c970a37581">Join our newsletter</a> + and follow all project news;</li> +<li><a href="https://kiwitcms.readthedocs.io/en/latest/contribution.html">Become a contributor</a> and an awesome open source hacker;</li> +<li><a href="/#subscriptions">Become a customer</a> and help us sustain development</li> +</ul>Testing and Continuous Delivery devroom, FOSDEM'252024-10-29T10:00:00+02:002024-10-29T10:00:00+02:00Kiwi TCMS Teamtag:None,2024-10-29:/blog/kiwi-tcms-team/2024/10/29/testing-and-continuous-delivery-devroom-fosdem25/<p><img alt="&quot;Cfp banner&quot;" src="/images/fosdem/2025/banner.png" title="Cfp banner"></p> <p>Attention testers! On behalf of the <a href="https://fosdem-testingautomation.github.io/"><em>Testing and Continuous Delivery devroom</em></a> we'd like to announce that call for participation is now open.