Introduction

Purpose and scope

Migrate core ExtJS components for Admin WI from ExtJS 4 to ExtJS5

Ticket NumberTT#393292
Target Build
MR48-0
Affected ComponentsPortaAdmin
Document Start Date2015-05-18

Collaborators

Business Department

Development Department

Testing and Support Departments

Definitions, acronyms and abbreviation

  • WI  web interface;
  • Ext JS  MVC/MVVM JavaScript framework for building cross-platform web applications.
  • MVC/MVVM  model-view-controller/model-view-view model  design pattern

References

  1. ExtJS5 critical bugs

Specifiations

Create "Business requirements" Create "Software requirements" Create "Design requirements"

Testing plan

Testing of the Migration to ExtJS5

Feature integration guide

It is auxiliary maintenance description which carries information about how to deploy and configure developed solution, its limitation and usage particularities. This chapter should be prepared as separate document.

10 Comments

  1. Unknown User (psv)

    There was special section "References" in template for additional information like "ExtJS5 critical bugs"  so I suggest to restore it. BTW the us also duplicated links on testing plan.

    1. I returned back "References" section.

      Duplicated links of testing plan occurs due to displaying the child pages. I've removed this block from template. Most of the child pages are created for already existent sections on the page (like testing plan, spec. and so on) I think "child" block is not neccessary for default template at all.

  2. Unknown User (psv)

    The child block is currently needed to automatically display Business Requirements, Software requirements and Design Requirements (and Testing Plan as well when we will add some basic template for it). The only alternative  is to add link on  newly created child pages manually but I am afraid that people will forgot to do this (sad)

    1. It's not good idea to keep child block only for Spec section, because there can be a lot of other child pages. I see that we have buttons "Create Business/Software/Design requirements". It would be better to add link to the created page automatically when user clicks this very button (creates some requirements). In such a case we avoid missing the links to mentioned pages and avoid duplication of other child pages.

  3. Unknown User (psv)

    • "It would be better to add link to the created page automatically when user clicks this very button" - sure, but currently it doesn't work in such way.
    • "because there can be a lot of other child pages" - actually on next level should be only 4 document. I don't see a reason to create lot of child pages.
    1. I just want to say that separate link on each section would be more preferable than all links in one place (via child box)

      "only 4 document" For example, this very project contains child page "critical bugs". Link to this page will be displayed in Specification section too. However, I don't think that this is supposed to be.

       

  4. Unknown User (psv)

    The whole project page is designated for handling new software functionality. That is why it has particular structure and in this structure "testing" is just a sub-part of the whole project.

    So ideally "critical bugs" page should go under "Testing plan" section/page.

    BTW If there are some purely QA specific projects then they should utilize some more specific templates for them.

    1. > So ideally "critical bugs" page should go under "Testing plan" section/page.

      As you wish. Should I move it accordingly?

      1. Unknown User (psv)

        Well, I don't think that it is worth to spend time on it now (smile)  Initially it was my attempt to guide project page in "proper" direction (according to my believing). But as soon as this page fulfilled its purpose we can leave it as is. 

         

        1. > I don't think that it is worth to spend time on it now

          It really takes several seconds, actually.

          > Initially it was my attempt to guide project page in "proper" direction (according to my believing). 

          Then, let's do it right and keep it in "proper" way for the future.

          Moved.