Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate "Performance demanding web parts in transformations" module to V4 report #232

Closed
6 tasks
ChristopherJennings opened this issue Apr 25, 2019 · 1 comment
Closed
6 tasks

Migrate "Performance demanding web parts in transformations" module to V4 report #232

ChristopherJennings opened this issue Apr 25, 2019 · 1 comment
Labels
groomed Well-defined and ready to be worked on help wanted This is an opportunity for anyone to contribute report migration
Projects
Prioritization Kentico Inspector V4

Comments

@ChristopherJennings
Copy link
Contributor

ChristopherJennings commented Apr 25, 2019 •
edited

Overview

We should migrate the Performance demanding web parts in transformations module to the new V4 report format.

Definition of done

  • Code and Scripts are ported to KenticoInspector.Reports project in a dedicated folder for the report.
  • Scripts are referenced via constants in a static class.
  • Scripts are refactored to return simple results that are mappable to simple classes.
  • Report logic is covered by unit test for a clean result
  • Report logic is covered by unit tests for all known dirty results
  • Useful, non-specific logic is abstracted to services or helpers.

Note: The Class/Table Validation report (and it's tests) is a good, simple example of the main concepts.

Additional Details

  • New name: Transformation Performance Analysis
  • Tags: Portal Engine, Performance, Transformations
@ChristopherJennings ChristopherJennings added help wanted This is an opportunity for anyone to contribute groomed Well-defined and ready to be worked on report migration labels Apr 25, 2019
@ChristopherJennings ChristopherJennings added this to the 4.0 milestone Apr 25, 2019
@ChristopherJennings ChristopherJennings added this to To do in Kentico Inspector V4 via automation Apr 25, 2019
@ChristopherJennings ChristopherJennings added this to Priority in Prioritization via automation Apr 25, 2019
@ChristopherJennings ChristopherJennings mentioned this issue Apr 25, 2019
Closed
@ChristopherJennings ChristopherJennings moved this from Priority to Medium in Prioritization Apr 25, 2019
@kentico-ericd kentico-ericd removed this from the 4.0 milestone Aug 8, 2023
@kentico-ericd
Copy link
Member

As we are now mainly supporting K13, this is not applicable

Kentico Inspector V4 automation moved this from To do to Done Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
groomed Well-defined and ready to be worked on help wanted This is an opportunity for anyone to contribute report migration
Projects
Kentico Inspector V4
  
Done
Prioritization
Medium
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ChristopherJennings @kentico-ericd