There are 4 typical levels of Testing in Software Testing:
a module is the smallest functional part of a program or application that cannot function separately only in combination with other modules. However, after the development of this module, we can already start testing and find inconsistencies with our requirements. Unit testing consists of testing this single unit as part of a program, assuming that it is only a unit.
the next level of testing, which is carried out after Unit testing. After we have tested our individual modules, we need to conduct integration testing to make sure that these modules work successfully in conjunction with each other. In other words, we test 2 or more related modules to check that the integration was successful and without obvious bugs.
the testing level in which we test an entire system or application that has been fully developed and is already ready for a potential release. At this level, we test the system, the application as a whole, conduct testing on all required operating systems or systems (if a desktop application) and conduct all the required tests such as functional, security testing, usability testing, performance testing, load testing, etc. ...
after the complete completion of the System Test, the product passes the level of Acceptance Testing, usually carried out by the customer or any other interested parties, in order to ensure that the product looks as originally required and was specified in the product requirements. Acceptance Testing can also be performed after each of the above test levels.
In my team we track tickets deviation by using two things:
Jira filters subscription for cases where we need plain(to one person/lead/manager) notification, but without fields analysis
https://github.com/dgroup/lazylead for cases where we need automatically check ticket fields, comments, links and alert corresponding person, assignee or reporter. Please note that i'm author of https://github.com/dgroup/lazylead app.
How should DevOps be used for managing repeat test runs?
To repeat test, we could to insert parameters in test steps:
Create a parameter by typing a name preceded by "@" in the actions and expected results of test steps
You could check this document Repeat a test with different data for some more details
Listing all possible test case names which could be extracted out of the scenario provided and classifying them in terms of priority and positive/negative/types is test case enumeration. Kindly comment if you need anything, here is an example for better understanding. Enumerate test cases for Login:(Classifying priorities into P1>P2>P3) Positive cases include:
P1-Verify the login dialog box
P1-Verify the login id
P1-Verify the password
P1-Verify the submit button
Negative cases include: 1. P3-Verify logging in with empty id and password fields
Note: Haven't covered all the test cases.
If we mean a table field, then
WHERE table_schema = 'database'
AND table_name = 'table'
AND data_type IN ('decimal','float','double');
If we are talking about a field in a certain data set, then in the general case, no way
How using a query you can parse a string and count the characters after the decimal point
(LOCATE(SUBSTRING(1.1 FROM 2 FOR 1), field) > 0) * LENGTH(SUBSTRING_INDEX(field, SUBSTRING(1.1 FROM 2 FOR 1), -1))
If you are convinced that tricks with a decimal separator are not expected, then simply do the following:
(LOCATE('.', field) > 0) * LENGTH(SUBSTRING_INDEX(field, '.', -1))