Skip to content

Testing new version before release

Jump to bottom
Nikolay Alipiev edited this page Jan 26, 2022 · 34 revisions
  • CLI
  • Schematics for Angular
    • igniteui-angular & ng-add schematic
    • @igniteui/angular-schematics & other schematics
  • CodeGen

CLI

Let's say that we have alpha/beta/rc tagged in the CLI - e.g. 9.0.5-beta.0.

Note: To release package follow the publishing new version topic, just release alpha/beta/rc instead of official version.

npm i [email protected]

We used to follow the Getting Started with Ignite UI CLI topic and test the generated Angular projects. However, here is a more detailed list of what should be generated and what should be tested at the end of the day. The next sections cover testing Angular project. The same testing should be valid for other technologies if the release is specific for them, or when we have a major release. The common case is to test Angular project because it is used by CodeGen.

Angular

Wizard

Using the wizard (step by step prompt):

  • empty project
  • a project with all the components and scenarios
  • a project with a component or scenario with login and custom theme.
  • authentication project

Commands

Using commands from the topic Getting Started with Ignite UI CLI:

  • empty new project
  • at least adding one component and one scenario (testing all the components with the wizard above will guarantee properly generation for other components)
  • authentication project
  • when there is a major release it is good to test both free and licensed packages.

Checklist

When a project is generated you need to test the following:

  • console errors (for a project with all the components you need to navigate through all the samples)
  • proper UI and experience for each of the samples
  • no lint errors
  • passing tests

For the above, you can use the VS Code npm scripts window in the Explorer tab and start each command them from there:

Other frameworks

For other projects like angular wrappers, react, react wrappers and web-components testing should be generating a project with all the components and again following the checklist.

Schematics for Angular

igniteui-angular - ng-add

Testing ng-add schematic for the igniteui-angular. This is our only schematic that is in the igniteui-angular project. Others are in the @igniteui/angular-schematics.

In order to test ng-add schematic you need to have a project (it may be empty), created with Anagular CLI (npm install -g @angular/cli)

ng new

Note: Use SCSS for styling

In order to test properly ng-add schematic the igniteui-angular beta package should have reference to the alpha/beta/rc package of @igniteui/angular-schematics. In that case [email protected] have reference to the @igniteui/[email protected]. Then you can run:

ng add [email protected]

If everything is successful then you can a component or a scenario, following this topic:

ng g @igniteui/angular-schematics:component grid newGrid

@igniteui/angular-schematics

When you have tagged a version of the CLI, then it also produces a package for the @igniteui/angular-schematics

npm i -g @igniteui/[email protected]

and create a project with the schematic.

ng new --collection="@igniteui/angular-schematics"

Then you can follow the wizard and generate a project with some scenarios and components and validate with the checklist.

CodeGen

ng new test-proj-codegen --collection=@igniteui/angular-schematics --theme=Custom --template=side-nav --skipInstall=true

Clone this wiki locally