olegood / boosti Goto Github PK

Add basic authentication for endpoints call.

Introduce pre-commit message check configuration.

All commit messages should start with ticket/issue number.

Add build info in footer section and introduce the API for getting this information.

API:
GET /api/build-properties

{
  "artifact": "boosti-web",
  "name": "Boost TI",
  "time": "1643359627212",
  "version": "0.1-SNAPSHOT",
  "group": "boosti",
  "timestamp": "2022-01-28T08:47:07Z"
}

Example:
Version: 0.1-SNAPSHOT

Create CSS layout including:

• header
• three unequal columns
• footer

Add simple placeholders for these elements.

Use in-memory database to store questions, answers (optional) and tags.

Create page called "Import" with elements:

• choose file to upload (browse)
• upload button
• uploading result

Subtasks:

• create "Import" page
• add navigation to "Import" page through top navigation bar
• results: "Success", "Failed" (with fail reason)
• in case of successful uploading there is a link to "Questions" page

Introduce Material UI components.

See for details:
https://mui.com/

Introduce failsafe Maven plugin and move JaCoCo threshold check into it.

Naming Conventions

Unit Tests

• suffix 'Test'

Integration Tests

• suffix 'ITCase'

Create dedicated screen for adding questions (topic and text are required).

Introduce API tests based on REST-assured test dependency.

Introduce new API:
DELETE /api/questions

Clean up deprecated code and Questions (old) view.

See for details: #23

Create initial client structure (ReactJS).
Create landing page that lists all the questions and grouped them by topic.

Example:

Maven

• How could we build project?
• What version of Maven do you use?

SQL

• What is DML?

Description

Enable disabled API tests after Basic Authentication implementation:

• EndPointBuildPropertiesAPITest
• EndPointQuestionsAPITest

Most probably it is necessary to specify header information.

Tasks

• enable EndPointBuildPropertiesAPITest
• enable EndPointQuestionsAPITest

Fill pom.xml with contributors list, artifact name etc.

Blank screen when choose file to upload in Firefox.

Preconditions

• Client: Firefox
• Version: 0.2

Steps to Reproduce

• Open Firefox
• Navigate to "Import"
• Click "Browse" and choose a file

Actual:
Console:

Uncaught TypeError: lastModifiedDate is undefined

The above error occurred in the <FileInfo> component:

FileInfo@http://localhost:3000/static/js/bundle.js:574:7
div
div
./node_modules/@emotion/react/dist/emotion-element-699e6908.browser.esm.js/withEmotionCache/<@http://localhost:3000/static/js/bundle.js:2603:66
Container@http://localhost:3000/static/js/bundle.js:13157:82
ImportContainer@http://localhost:3000/static/js/bundle.js:719:90
div
./node_modules/@emotion/react/dist/emotion-element-699e6908.browser.esm.js/withEmotionCache/<@http://localhost:3000/static/js/bundle.js:2603:66
Typography@http://localhost:3000/static/js/bundle.js:28167:87
div
./node_modules/@emotion/react/dist/emotion-element-699e6908.browser.esm.js/withEmotionCache/<@http://localhost:3000/static/js/bundle.js:2603:66
Box@http://localhost:3000/static/js/bundle.js:35221:72

Expected:
File is chosen and ready to be uploaded. File information is OK.

Description

checkstyle published a release: 10.1

Code snippet

<puppycrawl.version>10.1</puppycrawl.version>

Tasks

• update checkstyle version (puppycrawl) to 10.1

Create simple web-project based on following languages and tools:

• Java 17 (LTS)
• Apache Maven 3.8.4
• Spring Boot 2.6.3

Introduce ArchUnit for implementing some demo rules that check overall architecture requirements.

Create initial data model (Question) and some API for data retrieving.

Example:
GET /api/questions?topic=Java

Navigating to 'Import' for the first time shows an error in console:
react_devtools_backend.js:4061 Warning: validateDOMNesting(...): <ul> cannot appear as a descendant of <p>.

Introduce new domain object - category. Each question has to be attached to category (one-to-one).

• New domain entity - Category
• Question's topic is now deprecated
• API supports saving question with category

Description

Examine each changeSet in db.changelog-1.0.xml and provide rollback action.

Tasks

• add rollback actions to each set

Introduce JaCoCo plugin and set baselines:

• overall the project codebase (min: 80%)
• per class (min: 80%)

Add missing tests to reach these numbers.

Description

Test case QuestionServiceImplTest#shouldReturnAllQuestions was fully replaced with Spock fixture QuestionServiceImplSpec#service should return all questions from repository in 83d659c

Reduce time of test running: 618ms -> 107ms

See for details: 83d659c

Tasks

• delete unused QuestionServiceImplTest#shouldReturnAllQuestions
• delete unused QuestionServiceImplTest#from(java.lang.Long, java.lang.String)
• delete unused QuestionServiceImplTest#from(java.lang.String)

Create temporary drawer menu that opens from the left side.

Introduce new API:
DELETE /api/questions/{id}

Include instructions for failsafe plugin running.

Set CORS for all requests.

Todo: TDB

Refactor component and use hooks: useState, useEffect etc.

Description

New version of Spring Boot has been released. Keep the version up to date.

See the pom.xml:

<parent>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-parent</artifactId>
  <version>2.6.5</version>
  <relativePath/> <!-- lookup parent from repository -->
</parent>

Tasks

• checkout the latest version of Spring Boot and update it in pom.xml

Mark all the code used for Questions as deprecated.

Mimic the behavior on data grid view:

• select multiple questions
• export selected questions

See for details: #24

Description

Add missing frameworks and libraries.

Tasks

• add info about Checkstyle
• add info about JPA/Hibernate

Introduce ESLint and follow JS code best practices.

Introduce a separate type of tests - API.

All the tests that call RESTful API through Rest Assured will be called "API tests".

• change prefix for all the tests that call REST API to APITest
• ensure API tests run as part of the full build

Set up Swagger 2

Create sample classes for parsing data from valid JSON and XML files.

Add simple checks:

• avoid star import
• check missing Javadoc

Do not fail the build if any violations found.

Description

Since roles hierarchy implemented, no need to combine roles anymore.
Code of UserRolesAttribute.java could be safely removed.

P.S. This approach could be used in case of permissions-based solution (YAGNI).

Tasks

• delete unused UserRolesAttribute
• delete unused UserRolesAttributeTest
• delete unused UserRolesAttributeSpec
• move User to domain package

Change favicon.ico for::
https://iconarchive.com/show/red-orb-alphabet-icons-by-iconarchive/Letter-B-icon.html

Introduce Selenide as tool for UI (acceptance) testing.

Ensure uploading CSV follows comma-separated values convention.

• add validation for CSV file
• upload only valid CSV file
• process commented lines correctly (starts with dash #)

Description

Review README.md file and keep all the languages, tools and frameworks up to date.

Tasks

• add recently introduced languages and frameworks
• wrap used tools/languages etc. with URLs

Create simple API for CSV upload with comma-separated lines.

Example:
POST /api/upload

Create About page and migrate to app navigation bar from MUI library.

Export selected questions into downloadable text file.
Add timestamp when file was generated.

• introduce Question identifier